Relax pyarrow version constraint - #285
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #283
Depends on #286: allowing current pyarrow releases makes Python 3.12+ environments resolve zarr 3.3, so the chunk-type compatibility fix must land first.
Removes the
pyarrow<20cap while retaining the existing minimum, and adds a metadata regression test confirming pyarrow 23.0.1 satisfies the declared requirement.Tests: focused metadata pytest and pre-commit on changed files. The current Python 3.12/3.13 CI failures reproduce #284 and are resolved by #286.