Open tomvothecoder opened 1 week ago
This issue was recently fixed in xESMF by https://github.com/pangeo-data/xESMF/pull/373. We need to wait for a new release of xesmf
for this to be carried over, although we still might want to constrain numpy <2.0.0
for at least another year maybe?
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: https://github.com/pangeo-data/xESMF/issues/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