SPEC0 compliance: numpy >= 2, zarr >= 3 #11107
Draft
+145
−477
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
dcherian
force-pushed
the
spec0
branch
2 times, most recently
from
057c178 to
507c30d
Compare
- The minimum versions of some dependencies were changed: ===================== ========= ======= Package Old New ===================== ========= ======= boto3 1.34 1.36 cartopy 0.23 0.24 dask 2024.6 2025.1 distributed 2024.6 2025.1 h5netcdf 1.4 1.5 iris 3.9 3.11 lxml 5.1 5.3 matplotlib 3.8 3.10 numpy 1.26 2.0 packaging 24.1 24.2 rasterio 1.3 1.4 scipy 1.13 1.15 toolz 0.12 1.0 ===================== ========= =======
|
I believe numpy 1.26 drop was suggested to be delayed until end of Q2 |
Contributor
Author
|
Can you link to a thread where this was discussed please? |
|
apache/arrow#48473 I'm for dropping numpy 1.26 (as you can see from the #1 issue above) |
Contributor
Author
|
Interesting. thank you! |
dcherian
changed the title
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.
We can bump to
zarr>=3.0. I suspect this might be controversial so that change is in the second commit.The first one bumps the following: