-
-
Notifications
You must be signed in to change notification settings - Fork 776
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support NumPy 2.0 #8306
Comments
Just to make sure: the plan is for 14.0.0 to completely match NumPy 2.0? Which probably means only testing against NumPy 2.0 in all CI, since there is no way to match 2.0 and 1.26 at the same time? |
Yes, our current plan is to match CuPy v14 API with NumPy 2.0, and only test against NumPy 2.0+. |
I'm going to work towards this, starting with the python api, NEP 52. |
This (tries to) build artifacts based on Evgeni's PR to CuPy which should have most fixes needed to run with NumPy 2 and thus allow testing downstream projects with NumPy 2 if they also need CuPy. This includes most/all necessary Python fixes as well as fixes to make promotion align with NumPy (NEP 50). See also: * cupy/cupy#8323 * cupy/cupy#8314 * cupy/cupy#8306
Regarding NumPy 2.0 support, CuPy currently:
This means users cannot install/import CuPy in NumPy v2 environment. I'm thinking it's better to ship CuPy v13.2.0 release that includes:
before the NumPy 2 ship date. |
That would be great. I think not matching exactly all the promotion semantics and missing a few new functions is fine, as long as it imports correctly indeed. |
Make CuPy APIs compatible with NumPy 2.0 馃殌 Ref: #8269
Major tasks include:
The text was updated successfully, but these errors were encountered: