-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
BUG: Failed to compile numpy on python3.14.0a1 #27623
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
Comments
After some more research this might be caused by this Cython issue: cython/cython#6426 caused by underlaying cpython bug python/cpython#125868. It should be already fixed on cpython git, but I will probably wait for a cpython release before I test it again. |
Not yet I'm afraid. You could potentially skip compiling Cython itself with the environmental variable |
So in the end I tested it again from PR python/cpython#125876 and the compilation worked! |
It's unlikely we'll start testing NumPy against CPython releases until the first beta release, when the ABI stabilizes. If we supported it earlier than that we'd need to adapt to upstream changes which then might get backed out or iterated on in a way that would be obnoxious to deal with via CI. Waiting until the beta happens is much more sustainable. If you want to send in patches to fix build errors on 3.14 please feel free to if it's a reasonable change and isn't contingent on something that might be backed out upstream. Closing as not planned because building against 3.14.0a1 isn't something we're trying to support. |
Uh oh!
There was an error while loading. Please reload this page.
Describe the issue:
I tried to compile numpy on dockerized python3.14.0a1 and got the following error. Not sure if the issue is in numpy or cython though. I know python3.14 is not out yet, just getting ready for it :)
Reproduce the code example:
Put the following into ./Dockerfile:
and run
docker build .
Error message:
Python and NumPy Versions:
python 3.14.0a1
numpy 2.1.2
Runtime Environment:
No response
Context for the issue:
No response
The text was updated successfully, but these errors were encountered: