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
more fixes for NumPy2 #6100
more fixes for NumPy2 #6100
Conversation
One CI run failed to update with apt, and a windows/python3.13 one failed in |
LGTM. Thanks.
|
3.0.x commit 4f3c1ba |
I now see C compile failures in 3.0.x, both in C and C++:
|
Huh. I tested this with python3.11, maybe something changed with python3.12? Investigating... |
Ahh, of course. This needs latest numpy HEAD to pull in the changes made in numpy/numpy#26080 after the release of 2.0.0b1, so it will fail until the release of 2.0.0rc1. So what should be done here?
|
Another option is to pin 3.0.x to use cython/test-requirements-312.txt Line 1 in 3113c7f
|
I can live with the failures for the time being, as long as we know where they come from and that they'll go away in the not so distant future.
|
Continuation of #6076 to make tests pass on NumPy2 and still support NumPy1.
The complex changes incorporate the fix for numpy/numpy#26029. Unfortunately on C++, NumPy no longer supports
a[1].real += 1
. It still works in C, but not in C++. This is documented in the migration guide (last paragraph in that section).