Closed SeanBryan51 closed 5 months ago
I reproduced your error.
This worked for me
mamba create -c conda-forge -c accessnri -c coecms -y -n payu-install-test-310 python=3.10 payu=1.0.30
$ conda activate payu-install-test-310
$ which payu
/scratch/tm70/aph502/conda/envs/payu-install-test-310/bin/payu
(payu-install-test-310) (base) [aph502@gadi-login-02 scratch]$ payu -h
usage: payu [-h] [--version] {archive,build,collate,ghsetup,init,list,profile,push,run,setup,sweep,sync} ...
positional arguments:
{archive,build,collate,ghsetup,init,list,profile,push,run,setup,sweep,sync}
options:
-h, --help show this help message and exit
--version show program's version number and exit
I used mamba
for the build because it is so much faster.
The equivalent python-3.11
build also worked:
mamba create -c conda-forge -c accessnri -c coecms -y -n payu-install-test-311 python=3.11 payu=1.0.30
Is that an acceptable work-around?
I note we've not got yamanifest
deploying to accessnri
, so currently you will also need to use the coecms
channel when installing payu
.
Thanks Aidan, your work-around works for me. I'll close this issue.
Installing
payu=1.0.30
in a bare custom conda environment on Gadi seems to fail:To reproduce:
Note: these instructions assume you have done the necessary steps for creating personal conda environments found at http://climate-cms.wikis.unsw.edu.au/Conda#Creating_personal_environments