-
Notifications
You must be signed in to change notification settings - Fork 121
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
ESMValTool environment is incompatible with iris >= 3.3.0 #2945
Comments
For reference, we are working on a bugfix release for esmvalcore=2.7.1 that will allow iris=3.4 in ESMValGroup/ESMValCore#1848 - we've got a couple roadblocks at the moment, but am sure we can fix that asap 🍺 |
we have now released |
this has been solved with the new bugfix release v2.7.1 of esmvalcore, see the development install test - mind you, that particular one fails due to an issue with shapely, which is documented in #2965 - the conda package is still using the older iris due to the pin on cf-units though, but we can open a new issue for that 👍 |
Thanks @valeriupredoi and @bouweandela for all your work on this release!! That's awesome, with this I can finally finish ESMValGroup/ESMValCore#1664 in January 🥳 |
our pleasure, Manu! Enjoy AGU and happy holidays, bud 🎄 |
Thanks, happy holidays 🥳 |
I noticed that our current ESMValTool environment still contains
iris=3.2.1
, even though v3.3.0 is available since September (tested locally and on GitHub Actions).Pinning
iris>=3.3.0
in theenvironment.yml
file gives the following error during installation:Since there are many cf-units version >=3.1, I guess the error is misleading here and the problem comes from another package conflict.
I tried the same with updating ESMValCore's environment, in this case
iris=3.3.1
was loaded.The text was updated successfully, but these errors were encountered: