Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Discussion: Problems/Solutions when using conda for reproducible environments. #2997
I'd like to open a discussion about issues that need to be solved to make conda a real solution for producing reproducible environments.
A few of the issues that I noticed are:
This is related to a discussion started in conda-forge/openblas-feedstock#10
@ocefpaf and others, please add other problems or solutions to my issues in this thread.
@conda-maintainers If you think there is a better place to discuss this "meta"-issue then please feel free to redirect this to the proper channels.
I guess it is hard to rely on conda for that specific issue b/c we are asking the
For cases like that I rely on docker or a two-step install where I pin
I cannot say much about 2 and 3 as I haven't stumbled upon them (yet).
I think I've heard that the long term goal for conda is to be installable via pip and not depend on a miniconda installation. If this is still the goal then it should be possible for conda to bootstrap itself into an environment and then install the rest of the packages in the
Nope. In some cases you don't want true separation anyways. For example system libraries glibc on Linux or libSystem on Mac, we want to use and do not want to package them. Similarly there are some other libraries that are tied to the system and it would be a bad idea for us to package them or otherwise not use the system ones. Though I do get the drift of your question and note that you have a point.
Yes, this can happen and is known to cause problems in some cases. It's not clear to me whether those problems are easily solved in
with regards to:
As conda is getting more traction, it's time for the project to pay serious attention to backwards compatibility. Ideally, you would always be able to install an environment.yaml file generated with an older conda.
I don't understand the issue in this case -- but if the conda version used to created the environment.yaml file were preserved -- then newer versions of conda would know which "strategy" it should use to re-install the environment. So you wouldn't need to actually use an older version of conda.