-
Notifications
You must be signed in to change notification settings - Fork 33
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
Numpy 2.0 compatibility issue #742
Comments
@mauzey1 this might be worth watching as the current rc2 release (as of today) becomes the final version. I am curious if this has anything to do with the very old unsupported cdat/cdtime library, or with the evolving C-API changes (here, also see https://numpy.org/devdocs/numpy_2_0_migration_guide.html) |
16 June 2024 is now the official release date for numpy 2.0 (see here), so we should make sure CMOR 3.9.0 works with this new library! As the release date is now set, pushing the CMOR 3.9.0 milestone delivery out a week to enable testing is a good idea indeed - 28th June 2024 |
A recent conda-forge build for CMOR that updates NumPy to 2.0 encountered the following error.
I think this should be resolved by replacing
numpy.lib.utils.get_include()
withnumpy.get_include()
in setup.py.in.cmor/setup.py.in
Line 6 in 7714266
The text was updated successfully, but these errors were encountered: