Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NumPy 2.0 support #1818

Closed
jakirkham opened this issue Apr 25, 2024 · 3 comments
Closed

NumPy 2.0 support #1818

jakirkham opened this issue Apr 25, 2024 · 3 comments

Comments

@jakirkham
Copy link
Member

NumPy 2.0 is coming out soon ( numpy/numpy#24300 ). NumPy 2.0.0rc1 packages for conda & wheels came out 3 weeks back ( numpy/numpy#24300 (comment) )

To prepare for NumPy 2.0, it might be worthwhile to start testing against NumPy 2 in CI

NumPy has put out a migration guide. More details are in the release notes

Also as NumPy is tracking ecosystem support for NumPy 2.0, it would be helpful to share Zarr's current support status in issue (with any plans): numpy/numpy#26191

@jakirkham
Copy link
Member Author

jakirkham commented Apr 25, 2024

This will depend on migrating Numcodecs: zarr-developers/numcodecs#521

Edit: Numcodecs appears to pass tests with NumPy 2. Would still be good to test Numcodecs on CI, but that is not a blocker for Zarr

@jhamman
Copy link
Member

jhamman commented Apr 30, 2024

@jakirkham - do you want to try to drop in numpy==2 to the test matrix on the v3 branch here:

numpy = ["1.24", "1.26"]

@jakirkham
Copy link
Member Author

Fixed in the Zarr 2.x line with the PR linked below in 2.18.0

Also fixed in Zarr 3.x with the PR linked below

Closing as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants