I'm learing about Conda environment.yml and I'm not sure how to get Conda to find a certain version of dependancy

user_1704227 0
Viewed 1140

So I want to be able to build a environment that contains all libs I need for my project that im going to port to Docker.

So far my yml looks like this:

name: wt
channels:
  - anaconda
  - conda-forge
  - defaults
dependencies:
  - python=3.7.*
  - django=3.1.1
  - wagtail=2.11

So judging by the compatibility link I have the correct versions to run Wagtail but when I goto call conda env create -f environment.yml I get:

ResolvePackageNotFound:
  - wagtail=2.11

So I had a look on the Conda repo and I can't see a version 2.11. How would I get V 2.11 when can only get with v1 or v 2.7 which are both incompatible?

I have checked Wagtail Github and they are on version 2.7 but version 2.1 has LTS and thats why I would like to use it.

wagtail conda django python
1 Answers

Okay the documentation for creating a conda env is a bit spotty so I will do a clone & push later to fix that. So below is an example file of what I've discovered you can do with 'environment.yml'.

name: environment-name
channels:
  - anaconda
  - conda-forge
  - defaults
dependencies:
  - python=3.7.*
  - django=3.1.1
  - pip
  - pip:
    - wagtail==2.11.*

name:

Reference name of the environment.

channels:

These are the repositories on the CondaCloud that Conda searches when installing, example here. Please note that 'channel' means the package owners username.

dependancies:

The package you want to install may or may NOT include version numbers. if you want to declair a version number after a second/third/fouth decimal but not X decimal you may use a wildcard '*' to specify any. You also can include Pip but make sure you include it as a Conda dependancy first. It also worth mentioning that Conda uses a single '=' and Pip uses two '==' when specifying a version number.

user_17042270
Related