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
Support NumPy 1.24 #7243
Comments
The following tests need to be updated. https://ci.preferred.jp/cupy.linux.cuda-head/118940/ (full log):
-> #7245
-> #7286
-> Might be a NumPy issue:
-> Needs fix in CuPy. From the Release Notes:
-> out-of-bound Python integers
-> types of np.sin seems to have changed
-> out-of-bound Python integers
-> TypeError: arange() is only supported for booleans when the result has at most length 2.
-> out-of-bound Python integers The followings are still under investigation.
|
@seberg It seems that part of test failures are due to that
For example, I'm happy to file an issue in NumPy, but would like to check with you first whether this is considered a bug 😃 |
Thanks. We had numpy/numpy#22376 with numba noticing some of these. But I didn't see that the fix forgot about the transcendentals, and we had missed To some degree, numpy doesn't actually use the order but for arctan2 it seems to be used and this is indeed a bug! I will look into it we should try to make the 1.24.2 release. No need to open an issue, but happy if you do. |
@kmaehashi Would it be possible to add a task to the NumPy TODO list (and assign it to me if you like) for updating I give up following closely with upstream changes since 1. there's no notification mechanism we can rely on, 2. lack of bandwidth. But at least we can catch up whenever NumPy makes a new (minor or patch) release 🙂 |
Sounds good, added it to the task list (and the template). |
Tasks
.pfnci/schema.yaml
and.pfnci/matirx.yaml
.setup.py
(see [info] NumPy/SciPy new version pinning recommendation #4773.)numpy.array_api
tocupy.array_api
. -> Split to Support new features in NumPy 1.24 #7250docs/requirements.txt
to use the latest versions.The text was updated successfully, but these errors were encountered: