Conda env can't be specified by directory
IanSudbery opened this issue · 1 comments
We rarely build new conda envs in either the default conda install location, or ~/.conda these days, but rather specify locations with conda create -p PATH/TO/ENV
. However P.run(statement, job_condaenv=env)
expects env
to be a name, rather than a path, and looks up the path using conda env list
, which isn't much use for us.
I don't know what the solution might be?
Perhaps if we fail to find the named env, we should check if a driectory exists at the specified location and use that? There would be no way to check if it were a valid env though I don't think.
Yeh I think that would probably be the best approach.
We look for the path to the Conda env with this function anyway:
cgat-core/cgatcore/pipeline/execution.py
Line 179 in ae6e964
So we would check if its a path look to see if it exists and return it if it does. Would that work?