lock file?

[ben....@recursionpharma.com]

Hi all,

conda doesn't appear to have the concept of a lock file like other library management tools (e.g. Ruby gems and the python Pipfile https://github.com/pypa/pipfile). If you are unfamiliar with the concept a lock file allows you to specify libraries in your main file but the exact version is pinned in the lock file. This allows for easier automated updates. Does conda plan to add something like a lock file? 

It seems like the output of `conda env export` is pretty close to what one would need in a lock file. In practice is that what people use to help automate the locking and updating of dependencies?

Thanks,

Ben

[Michael Sarahan]

I think you're looking for https://conda.io/docs/user-guide/tasks/manage-pkgs.html#preventing-packages-from-updating-pinning

--
You received this message because you are subscribed to the Google Groups "conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to conda+un...@continuum.io.
To post to this group, send email to co...@continuum.io.
Visit this group at https://groups.google.com/a/continuum.io/group/conda/.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/conda/6d27b98d-57bb-4d36-aa19-e7b394ee28f1%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.

[ben....@recursionpharma.com]

Not quite. Pinning to a specific version in the actual env file is different than having a lock file that declares it. The difference is that the tool will update the lockfile automatically when you update your deps. That way the workflow is, update deps, run tests and do other verification that things don't break, and then commit the changes. This workflow can be mimicked with `conda env export` somewhat but requires extra steps.