Closed fabcor-maxiv closed 8 months ago
You are right that one would like to use this for whatever python version one intends to use, so the range is maybe not really necessary. One needs to either pass python version via command line or edit the file to get the wanted result.
Seems like something like this works:
conda create --file conda-environment-dev.yml python=3.9
and this fails (as we would want):
conda create --file conda-environment-dev.yml python=3.7
Yeah, thats what I had in mind, but not sure that passing python version will override whats i the yaml
, did you try ?
Yes, that is what I meant. I tried both the commands in my previous message.
We could document this somewhere, although I assume it is kind of basic conda knowledge. On mxcubecore we do not really have a good place to document this, but we could do it for mxcubeweb at least.
:+1: ok sounds good. It is basic conda knowledge and its, I would say, the expected behavior
Let's close this. See the following instead:
:+1: Thanks !
I wrote:
@rhfogh wrote:
@marcus-oscarsson wrote:
My intention is not to change the Python version range in Poetry
pyproject.toml
which is the one that declares what Python versions are supported by this library.The way I see it,
conda-environment-dev.yml
is only to set up a development environment quickly. Is there a way with the current version of this file to choose something else than Python 3.10 when creating the conda environment?