Open sadielbartholomew opened 1 year ago
Probably this relates to the following backward incompatible changes at ESMF release 8.4.0, namely as covered in the relevant Changelog entry:
The Python module name for ESMPy was changed in this release from “ESMF” to “esmpy” for better alignment with Python Enhancement Proposal (PEP) guidelines. This change will require user code changes! ESMPy users will have to do a global search and replace on their scripts to adjust to the module name change. Also notice that the internal ESMF source tree directory structure has changed, moving ./src/addon/ESMPy to ./src/addon/esmpy. This might affect anybody keeping an ESMF repository clone, and maintaining scripts that depend on the internal directory naming.
Hi @sadielbartholomew - is this closable, now? Thanks
Yes, please close this, though there are other aspects of the CI workflows I need to update at this point and am yet to find the time to do so. Shortly, I shall try to get it done.
The
esmf
library isn't being installed properly for ourtest-source-dist
CI workflow, so that it isn't available and therefore regridding capability depending on ESMPy is erroring out, for example as shown from this snippet in the logs from the recent job https://github.com/NCAS-CMS/cf-python/actions/runs/4551782556/jobs/8026279312?pr=627:ESMF did get installed OK for this workflow before, so something has changed. I don't have time to look into this before Easter, but note for that job, as an example, from a quick search through the logs, the library does get downgraded, which probably relates to the issue: