Raise informative error on Zarr V2 parsing with Zarr-Python<3.1.3 #829
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maxrjones
temporarily deployed
to
test-release
GitHub Actions
Inactive
7 tasks
TomNicholas
reviewed
Nov 12, 2025
TomNicholas
approved these changes
Nov 12, 2025
maxrjones
temporarily deployed
to
test-release
GitHub Actions
Inactive
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR builds on #822 to raise a more informative error if using the parser with older versions of Zarr-Python, which do not contain the necessary V2->V3 metadata conversion functionality.
To be merged after #828 to keep changes isolated
docs/releases.rstapi.rst