Closed aidanheerdegen closed 9 months ago
This could have been avoided if the CI includes the conda package build steps, and CD just installs the produced artefact.
Would be keen to add the package build as a CI step as a later, non-bandaid solution. Right now, to get the releases out the door, pinning the version of Python used to 3.11
will be good enough.
The CD step deploying to conda fails due to a missing import
imp
https://github.com/payu-org/payu/actions/runs/7382868756/job/20083209964#step:4:399
This appears to be a problem with python >= 3.12 due to that module being missing/deprecated
https://github.com/MultiQC/MultiQC/issues/2112