-
-
Notifications
You must be signed in to change notification settings - Fork 278
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
Comments
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 |
@jakirkham - do you want to try to drop in numpy==2 to the test matrix on the v3 branch here: Line 115 in 096c900
|
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 |
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
The text was updated successfully, but these errors were encountered: