I have a Python project that is dependent on a Conda environment and is itself normally built and installed into such environment before use. The work flow of the project is currently provided by a Cylc suite. So, imagine the root level of the project containing an
environment.yml file, a
setup.py file and a
An initial task of the suite creates a Conda environment under the suite’s share directory and installs the Python project in it. Subsequent tasks would activate the Conda environment to gain access to the project’s console scripts.
The advantage of this set up is such that the Conda environment is self-contained within the suite run time, and so has no reliance on specific Conda environments outside the suite. As long as a user has Miniconda (or equivalent) installed, then this suite is portable and does not pollute their environments or generates any namespace clashes.
This Gist contains a copy of the script run by the initial task:
(Sorry, actual suite is under a private GitHub repository, so cannot link to it.)
My understanding is that we are still going to use Conda to manage the complex Cylc 8 environment? If so, can anyone think of any issue with the Conda environment set up described above?