Skip to content

Instantly share code, notes, and snippets.

@caseywdunn
Last active January 7, 2018 00:19
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save caseywdunn/59c94fc81db53c5916ff9930b72d4e71 to your computer and use it in GitHub Desktop.
Save caseywdunn/59c94fc81db53c5916ff9930b72d4e71 to your computer and use it in GitHub Desktop.

Working with Conda

First, some nomenclature (see https://conda.io/docs/glossary.html for more):

  • A recipe is a flat directory that has the information needed to build a package
  • A package is a "compressed file that contains everything that a software program needs in order to be installed and run... You manage conda packages with conda."
  • An environment is a "directory that contains a specific collection of conda packages and their dependencies, so they can be maintained and run separately without interference from each other."

A typical workflow:

  • write a recipe, eg https://conda.io/docs/user-guide/tutorials/build-pkgs.html
  • Run conda build -n mytool . to build the package from the recipe
  • You could at this point upload the package to anaconda.org with anaconda upload
  • Create an environment with conda create
  • Install the package into the environment with conda install. If you are installing a locally built package, use conda install --use-local.
  • Activate the environment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment