-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
python3-numpy: update to 1.25.0. #44529
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that moving to the pep517 build style is a waste of time. We'll have to move to meson for Python 3.12 anyway, it seems. In the meantime, let's stick with what works.
I'll try to fix those, nothing seems too bad. Ideally we would wait until sagemath is fixed to push the numpy update. |
i686 and musl failed, I will work on them locally before I resubmit the PR. |
musl is this single failure:
Can reproduce with:
Indeed this is "incorrect" since it should choose a branch with positive real part (i.e Note this is also wrong in the 1.24.3 that is in void repo (but only on musl). |
Actually, this seems like a bug in musl libm:
Note that
For whatever reason |
See here: https://git.musl-libc.org/cgit/musl/commit/?id=aa2d23e57c9c95f0ffeb80cb035e5a5be52d8ef0 I didn't try it but it seems like that would do the trick; I'm guessing our musl is older than this commit. |
Don't worry about this failure; we can just ignore it for now. |
I have worked out the issues with sage; I will soon make a PR for an updated sagemath 10.0 patched with support for maxima 5.47.0, singular 4.3.2p2 and numpy 1.25.0 (which are the 3 updates that break it slightly). Ideally this PR should wait until sagemath is patched. |
This can be merged after #44624. |
Testing the changes
I enabled check, and I'm currently testing with sagemath to see what fails and fix it. So far I've only tried x86_64.
I didn't change the build-style to pep517 because that won't allow parallel build. For testing, a custom
do_check()
is needed in any case. Moreover, it seems numpy will soon move to meson for building so we may as well wait for that.@ahesford