-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
TSK: Make NumPy buildable on the nogil branch #26161
Comments
@lysnikolaou has some WIP changes that lets me build
Reloading will probably be fixed upstream but the others look like issues in numpy that bear a closer look. Additionally, all the cython and most of the f2py tests are failing due to a meson issue on 3.13 that meson is waiting on an upstream fix for. I'd like to get these tests fixed and add add 3.13 CI. I see a build matrix including a normal 3.13 build, and two 3.13 test runs with We might need to xfail or skip the cython or f2py tests for now. |
This is the |
python/cpython#116609 is merged, which fixed all the tests that depend on meson. I also just merged #26207 which fixes one of the tests and marked the limited API test as an xfail in #26229. I'm going to close this for and open followup issues about test failures with the GIL disabled (awesome we've gotten that far already!). I'm also going to set up bleeding edge CPython CI that can be converted into CPython prerelease tests once the first beta is cut. |
Awesome, nice work!
On a fork for now rather than on this repo? This is probably going to be failing regularly for the next weeks, with changes in CPython and Cython. |
Wasn't there a way to say "failure is OK" so that it shows up as orange and not as a failure? that would seem fine also. |
If there is, I'm not familiar with it. My understanding is that there's a feature to say which checks are required for merging, which we don't use. If you do use it, failing non-required jobs still look red but won't block merging. For us, I think any failing job will simply be red. |
There's no official feature for this, but there's a workaround explained on the feature request ticket. |
Oh wait, I read the proposal as "a new CI job for the no-GIL build", but on re-reading I think you meant one for the default CPython build. That seems fine by now; with beta 1 arriving in a couple of weeks I hope there won't be more than 1 or 2 more regressions that affect numpy anymore. |
Yeah, I guess |
That's right, just vanilla 3.13 CI. Nogil CI will have to wait until more stuff is stabilized. |
Currently the build fails with internal errors in cython (compiled using the latest
cython
master
branch):We can probably hack around this by disabling
np.random
for nogil python.The text was updated successfully, but these errors were encountered: