-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
PyPy 3.10 support for Numpy 2.0.0rc1 or later? #26141
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
Probably not, since it's not in the pipeline yet. @mattip may be able to say more about PyPy 3.10 support in general. |
If the project does decide to release wheels, I would suggest supporting x86_64 linux and maybe macos arm64 only. Windows support is failing on the weekly binary builds against pypy and I am not sure why, maybe some subtle interactions between PyPy's NAN and the expected values. |
Interestingly, when comparing NumPy windows-latest/pypy3.9-nightly with NumPy windows-latest/pypy3.10-nightly, these versions are (x)failing the same tests (also for the same reasons). For
The failures are distributed as follows: 2F in Because of this, there seems to be no reason to prefer pypy3.9 over pypy3.10. Again interestingly, when I run these four tests above on my Windows machine with PyPy3.9 nightly together with Numpy 2.0.0b1, there are no failures at all:
The other three tests above also pass without failures. Also, I've been testing my own Python package with PyPy3.9 and Numpy 2.0.0b1 without any problems (after making some minor adjustments which are also needed for cPython3.9 plus Numpy 2.0.0b1). So, maybe there is no serious cause for the test failures on Windows, and it would be good to switch to PyPy3.10 now so that people can test Numpy2.0.0 with PyPy3.10. |
Numpy 2.0.0b1 comes with pypy39 wheels but support for Python 3.9 has been (recommended to be) dropped since 2023 - Q4.
Will you have pypy310 wheels for the upcoming Numpy 2.0.0 release candidates?
The text was updated successfully, but these errors were encountered: