-
Notifications
You must be signed in to change notification settings - Fork 58
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
Build failures against NumPy 2.0 with GCC 14 #393
Comments
Hi All 👋 NumPy is planning to release 2.0 on June 16th ( numpy/numpy#24300 (comment) ). NumPy 2.0.0 RC packages for conda & wheels came out at the beginning of April ( numpy/numpy#24300 (comment) ) NumPy has put out a migration guide. More details are in the release notes If fitsio makes use of NumPy's C API (and produces wheels that use it), having a release of fitsio with wheels built against NumPy 2.0.0rc1 would be helpful to ensure NumPy 1 & 2 compatible wheels (as wheels built against NumPy 1 won't be compatible with NumPy 2). More details in this NumPy 2 ABI doc Also as NumPy is tracking ecosystem support for NumPy 2.0, it would be helpful to share fitsio current support status in issue (with any plans): numpy/numpy#26191 |
Thanks. We definitely have some work to do but it looks mostly mechanical. |
Does #394 solve the issues for you? |
Yes, it does. Thanks a lot! |
Thanks all! 🙏 Should we close this issue then? Or do you want to wait for a release? |
I'm thinking to close and make a release ASAP, but I'm happy to hear counterarguments. |
SGTM |
Feel free to close it. |
When using a stricter compiler (e.g. GCC 14) and building against NumPy 2.0.0rc2, the build fails over a bunch of type mismatches:
(the list is actually quite long)
The text was updated successfully, but these errors were encountered: