instead of using the command conda create --name esmvaltool 'python=3.7' && conda env update --name esmvaltool which works fine - the env updateing from a Py39 env that requests a Py37 is rough and leads to insolvability - I am going to suggest to the devs change it, if they don't do it we'll have to change the test ourselves :beer:
test
This is a recurring issue. I'm looking into it right now.
Update - cause found
The problem is that the conda incubator task uses a patched env file:
instead of using the command
conda create --name esmvaltool 'python=3.7' && conda env update --name esmvaltool
which works fine - the env updateing from a Py39 env that requests a Py37 is rough and leads to insolvability - I am going to suggest to the devs change it, if they don't do it we'll have to change the test ourselves :beer: