[conda] Package pinning when creating env from file

[Simon Ho]

When creating a new environment from a yaml file (conda env create -f
environment.yml), is it possible to additionally have conda pin the
packages to the versions specified within that file?

I know you can manually create a pinned file in conda-meta, but if I have
versions specified in environment.yml, it would seem sensible to also
automatically pin those packages during env creation

[Chris Withers]

Hi Simon,

Post by Simon Ho
When creating a new environment from a yaml file (conda env create -f
environment.yml), is it possible to additionally have conda pin the
packages to the versions specified within that file?
I know you can manually create a pinned file in conda-meta, but if I
have versions specified in environment.yml, it would seem sensible to
also automatically pin those packages during env creation

My experience has been that this is exactly how it works, can you give
some examples where it has not?

cheers,

Chris

['Simon Ho' via conda - Public]

For example, my environment.yml file might contain something like:

channels:
- defaults
- conda-forge
dependencies:
- numpy=1.12.*



When I create the env from file, it installs numpy 1.12.1, which is
correct. However, when I look in conda-meta, I dont see a pinned file.
Additionally, when I activate the env and run conda update numpy, it tries
to update numpy to 1.15.4

My expectation is that numpy will be pinned automatically so that it cant
accidentally be updated to any version greater 1.12.*

Post by Chris Withers
Hi Simon,

Post by Simon Ho
When creating a new environment from a yaml file (conda env create -f
environment.yml), is it possible to additionally have conda pin the
packages to the versions specified within that file?
I know you can manually create a pinned file in conda-meta, but if I
have versions specified in environment.yml, it would seem sensible to
also automatically pin those packages during env creation

My experience has been that this is exactly how it works, can you give
some examples where it has not?
cheers,
Chris

[Chris Withers]

|
-defaults
-conda-forge
-numpy=1.12.*
|
When I create the env from file, it installs numpy 1.12.1, which is
correct. However, when I look in conda-meta, I dont see a pinned file.
Additionally, when I activate the env and run conda update numpy, it
tries to update numpy to 1.15.4
My expectation is that numpy will be pinned automatically so that it
cant accidentally be updated to any version greater 1.12.*

Ah, okay, yeah, conda doesn't currently support that pattern, but I
wrote a thin layer over it that does:

https://picky-conda.readthedocs.io/en/latest/

cheers,

Chris