-
-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Ecosystem compatibility with numpy 2.0 #26191
Comments
Thanks - for JAX we are planning an 0.4.26 release in the next day or two which will be built against NumPy 2.0.0rc1. |
Also, in case you want to add it, we just released |
Thanks for putting this together Ralf! 🙏 This is incredibly helpful 🙂 |
Thanks @jakevdp, I added the info for both JAX and |
|
Also, here's where to track progress for cartopy : SciTools/cartopy#2339 |
Thanks @neutrinoceros, much appreciated. Added both packages. |
ContourPy 1.2.1 has just been released on PyPI (https://pypi.org/project/contourpy/1.2.1/) with NumPy 2 compatibility, most relevant PR is contourpy/contourpy#371. It is a compulsory dependency of Matplotlib. |
For PyArrow, it will be the upcoming 16.0 release that will be the first numpy-2.0-compatible release, but this will only be expected in around 3 weeks at the earliest (but normally certainly before the end of the month). |
Could we add OpenCV to this list? I filed a ticket here to track progress on a numpy 2.0 build for it. |
Thanks @ianthomas23, @jorisvandenbossche, @dkbarn - all info added to the table. |
JAX released 0.4.26 on pypi, which is compatible with NumPy 2.0. (NumPy folks: congratulations on your imminent v2 release!) |
mpl 3.8.4 is out, built with np 2 |
yt 4.3.1 is on PyPI and built with numpy 2.0.0rc1 ! EDIT(seberg): Added to table. |
|
Thanks for the update @MichaelHudgins, that sounds great. |
Thanks Michael! 🙏 |
Could we please add these issues to the table?
|
Please add CARMA to the table:
|
Use the NumPy 2 support in Pandas as the template. Update requirements to depend on NumPy 2 compatible versions (based on numpy/numpy#26191).
Thanks @jakirkham and @conradsnicta, all done. |
@jakirkham I've sent you an invite with triage permissions - please feel free to make edits directly (and thanks again for all the help!). |
Could this one for That project does not have a compatible release, and based on comments there seems to be planning a |
Thanks @jameslamb, added. |
Thanks Ralf! 🙏 Accepted 😄 Interestingly I'm not able to edit the OP though Guessing we would need edit privileges for that Maybe we could move this into another repo or HackMD where we could liberally hand out permissions for editing? What do you think? |
Could we please add these to the list as well? Sorry would do myself, but wasn't able to (as noted above)
|
Congratulations 🥳 Thanks Bas! 🙏 Have updated the table in my comment above to reflect this. Please let me know if I've missed anything |
Thanks for the work on this! Can we please add:
? |
Imagecodecs 2024.6.1 supports numpy 2. |
Thanks everyone! I made all requested edits.
I'd rather not move the authoritative version, so close to the finish line. Having an edit history with diffs is also useful. However, easily sync-able edits are useful, so here is an editable HackMD version: https://hackmd.io/B_zU26JfSI-703Xz85Ie_Q?view. Every user who is signed in to HackMD should be able to edit that. |
Hi all, torchvision 0.19 will be fully compatible with numpy 2.0. |
This list tracks the compatibility status of packages that depend on or support NumPy. If "compatible release on PyPI" does not say "yes" but a version number is listed: this is based on plans announced in a tracking issue or other communication by the authors of the package.
Maintainers: please feel free to edit directly (please refresh the page first to avoid overwriting edits from others!). Others who want to update things: please do comment, or feel free to ping me elsewhere.
<2
upper bound for 2.16.1, requirements, lock fileThe text was updated successfully, but these errors were encountered: