-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Bug]: xESMF related issue "AttributeError: np.NaN
was removed in the NumPy 2.0 release. Use np.nan
instead."
#668
Comments
This issue was recently fixed in xESMF by pangeo-data/xESMF#373. We need to wait for a new release of |
Wow, existing Worse, it might prevent potential new [UPDATE] I have experimented a bit, and updated two test environments on two different servers. I don't know how dependencies and priorities work, but I ended up in both cases with It's only when I ask
|
I wonder if a year was sufficient because In our case, it looks like xESMF might be the only xCDAT dependency that breaks with numpy 2.0 which would mean we don't need to a year to remove the constraint. |
Turns out that one of our post-doc reported today that regridding in xesmf (0.8.6) was not working anymore, and it worked again when I downgraded numpy from 2.0.0 to 1.26.4. This was not an np.NaN error An intern had the same problem last Friday. I have also downgraded his numpy and asked him if this fixed the problem |
What happened?
xESMF is conflicting with
numpy>=2.0
, which is breaking the GitHub Actions build (here).I opened an issue in the xESMF repo here: pangeo-data/xESMF#370
What did you expect to happen? Are there are possible answers you came across?
Related code in xESMF: https://github.com/pangeo-data/xESMF/blob/530b804c28a9b4f64dd360384897c4c2b34ab8c3/xesmf/smm.py#L229
numpy <2.0
Minimal Complete Verifiable Example (MVCE)
No response
Relevant log output
Anything else we need to know?
No response
Environment
Latest xCDAT,
numpy>=2.0
andxesmf=0.8.5
The text was updated successfully, but these errors were encountered: