You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
PyPy 3.10 support for Numpy 2.0.0rc1 or later? #26141
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.
2F in _core\tests\test_api.py
2F in _core\tests\test_casting_unittests.py
10(x)F in _core\tests\test_strings.py
12F in _core\tests\test_umath.py
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:
>python
Python 3.9.18 (4133dd3122a1, Mar 27 2024, 07:16:40)
[PyPy 7.3.16-alpha0 with MSC v.1929 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
And now for something completely different: ``"Let's go." - "We can't" - "Why
not?" - "We're waiting for a Translation." - (despairingly) "Ah!"''
>>>> import numpy
>>>> numpy.__version__
'2.0.0b1'
The other three tests above also pass without failures.
I'm using Windows 10 Home 22H2 19045.4170.
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.
Activity
rgommers commentedon Mar 27, 2024
Probably not, since it's not in the pipeline yet. @mattip may be able to say more about PyPy 3.10 support in general.
mattip commentedon Mar 27, 2024
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.
lschoe commentedon Mar 28, 2024
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
pypy3.9-nightlyand forpypy3.10-nightly, respectively:= 26 failed, 47581 passed, 2690 skipped, 84 xfailed, 33 xpassed in 2235.08s (0:37:15) == 16 failed, 47595 passed, 2676 skipped, 94 xfailed, 33 xpassed in 2065.49s (0:34:25) =The failures are distributed as follows:
2F in
_core\tests\test_api.py2F in
_core\tests\test_casting_unittests.py10(x)F in
_core\tests\test_strings.py12F in
_core\tests\test_umath.pyBecause 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.
I'm using Windows 10 Home 22H2 19045.4170.
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.