You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an umbrella issue that is motivated by our dependencies environment being fairly patchy and out of date; there are some outstaning issues at play:
the need for NCL to be moved to an "optional dependency": ncl is lagging behind with every Python and co upgrade, specifically for us, it makes it impossible to:
unpin pandas - that will be done when we release ESMValCore v2.12 since the fix for pandas is there now
unpin numpy<2 ie upper bound - iris 3.11 is safe for numpy>=2 - we should free it too, and consider issues with diagnostics not being numpy2 compatible as they come, probably during the release process for v2.12; unpinning upper bound for `numpy done in Update environment: pin iris>=3.11, unpin cartopy and allow for numpy >=2 #3811
unpin r-base <4.3 - I can't remember why we are doing that, I need to look into it
The text was updated successfully, but these errors were encountered:
This is an umbrella issue that is motivated by our dependencies environment being fairly patchy and out of date; there are some outstaning issues at play:
ncl
is lagging behind with every Python and co upgrade, specifically for us, it makes it impossible to:esmpy>=8.6
numpy>=2
importlib_metadata <8
(predicated by olderesmpy
, predicated, in turn, by NCL)curl
, hopefully with a correctcurl=8.11
, caused by the issues it has with Julia installing packages, see Unpincurl
#3758cartopy
, see Unpin cartopy #3769 -> this is done in Update environment: piniris>=3.11
, unpincartopy
and allow fornumpy >=2
#3811 - it is safe to do that since we pin iris therepandas
- that will be done when we release ESMValCore v2.12 since the fix forpandas
is there nownumpy<2
ie upper bound - iris 3.11 is safe for numpy>=2 - we should free it too, and consider issues with diagnostics not being numpy2 compatible as they come, probably during the release process for v2.12; unpinning upper bound for `numpy done in Update environment: piniris>=3.11
, unpincartopy
and allow fornumpy >=2
#3811r-base <4.3
- I can't remember why we are doing that, I need to look into itThe text was updated successfully, but these errors were encountered: