Use consistent version string for zarr lower bound #487
+1
−1
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
3 tasks
Member
|
Thanks for the PR - build failures I think are due to a test I just pushed a fix for at #488 |
jdblischak
force-pushed
the
zarr-lower-bound
branch
from
e1f5258 to
d8291ca
Compare
Contributor
Author
|
I rebased my PR now that the test fix in #488 has been merged |
will-moore
approved these changes
Aug 27, 2025
Member
will-moore
left a comment
will-moore
left a comment
There was a problem hiding this comment.
My bad - Added the v in #413.
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.
Since support for zarr 3 is still a work in progress across the Python spatial ecosystem (eg spatialdata in scverse/spatialdata#969), the lower bound of
zarr >=3.0.0for ome-zarr 0.12.0+ is critical.Currently
pyproject.tomlhas avprepended to the version string. Whilepipcan properly interpret this version string, conda cannot, which has caused problems when packaging ome-zarr for conda-forge. Since the zarr maintainers do not put avin front of their version strings (PyPI release history), and none of the other version strings in ome-zarr'spyproject.tomlinclude thisv, would you please consider merging this PR to use a consistent version string for the zarr lower bound? Not only would this help conda-forge maintainers like me, but it would help any other community packaging efforts that rely on automated parsing ofpyproject.tomlto determine the package dependency network.xref: conda-forge/ome-zarr-feedstock#31, conda-forge/conda-forge-repodata-patches-feedstock#1068, https://github.com/conda-forge/ome-zarr-feedstock/pull/28/files#r2301294027