View source for Conda with Python (Reference Only)

Due to [https://www.datacamp.com/blog/navigating-anaconda-licensing licensing issues] with conda, we no longer recommend using Anaconda/Miniconda for package management or virtual environment management. We instead recommend the open source alternative [https://mamba.readthedocs.io/en/latest/index.html Mamba]

[[Mamba]] (Conda) is preinstalled on every StatDS server.

See [[Python virtual environments]] for how to set up Mamba. Instructions for setting up Anaconda/Miniconda have been migrated here for reference.

==Installing Conda==
===<code>conda</code> for your personal computer===
To install&nbsp;<code>conda</code> on your personal computer you can install anaconda or miniconda with an installer (works for Mac, Windows and Linux) or via command line. Anaconda takes up more space and comes with a decent amount of packages installed, whereas miniconda takes up much less space but doesn't come with packages installed (see [https://conda.io/projects/conda/en/latest/user-guide/install/download.html#anaconda-or-miniconda conda.io] for more commentary on the differences. For either installation, check the hash (a unique identifier of the object) to make sure you're not installing a bug (see [https://conda.io/projects/conda/en/latest/user-guide/install/download.html#id5 | conda.io] for how to check the hash on different OS). Generally speaking, Anaconda can be useful if you're&nbsp;new to programming. Miniconda has all the package-manager functionalities but requires you to install every single package in the environments, which is generally better if you want to manage your projects from scratch.

To install miniconda head here: [https://docs.conda.io/en/latest/miniconda.html docs.conda] and anaconda head here: [https://docs.anaconda.com/anaconda/install/index.html docs.anaconda].
===<code>conda</code> for your server===
To install <code>conda</code> on the server you need to use the command line all the way through (you cannot download anything from a webpage. As such, I recommend installing miniconda following these steps (for Linux systems):
#<pre>mkdir -p ~/miniconda3</pre><ol start="2"><li><pre>wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O ~/miniconda3/miniconda.sh
</pre></li><li><pre>bash ~/miniconda3/miniconda.sh -b -u -p ~/miniconda3
</pre></li><li><pre>rm -rf ~/miniconda3/miniconda.sh</pre></li><li><pre>~/miniconda3/bin/conda init bash</pre></li></ol>Similar steps can be followed to install miniconda from the terminal on Mac and Windows systems. See&nbsp;this [https://engineeringfordatascience.com/posts/install_miniconda_from_the_command_line/ link].

'''N.B. for Hydras.'''&nbsp;For reasons related to how Hydras directory system is setup, you will need an extra step to make sure miniconda is initialized and available every time you log into the server. The steps above populate your&nbsp;<code>.bashrc</code> file with a small script that initialized conda at log in, but this file is not sourced by Hydras. Instead, you need to create a&nbsp;<code>.profile</code> file (if it's not already there) and add&nbsp;the following line to it:<pre>source .bashrc</pre>
==Conda’s virtual environments==
A good tutorial on how to create a virtual environment with <code>conda</code> can be found at [https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#creating-an-environment-with-commands conda-io]

In a nutshell:
#To a&nbsp;'''create new environment'''&nbsp;with Python installed (note that <code>base</code> is your standard environment) you should run:<syntaxhighlight lang="bash">conda create -n yourenvname python=x.x</syntaxhighlight>


&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;where <code>x.x</code> is the python version you’d like to use. I might suggest starting with 3.11&nbsp;now.<ol start="2"><li>Then to '''activate your conda environment''', just run:<syntaxhighlight lang="bash">conda activate yourenvname</syntaxhighlight></li></ol>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;This will probably make your terminal show <code>(yourenvname) ...$</code>, whereas&nbsp;originally it should have read <code>(base) ...$</code>.<ol start="3"><li>To '''install packages''' in your local environment:
After activating (and before deactivating your virtual environment) you can just do<syntaxhighlight lang="bash">conda activate yourenvname
conda install [package]</syntaxhighlight></li></ol>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;An alternative to the second line is&nbsp;&nbsp;<code>pip install [package]</code><ol start="4"><li>To '''deactivate''' your environment:<syntaxhighlight lang="bash">conda deactivate</syntaxhighlight></li></ol><ol start="5"><li>To '''share''' virtual environments (useful for reproducibility):
To share your virtual environment (with collaborators or yourself on the server) you can make a <code>.yml</code> file that contains all the information about the packages you are using by first opening up the virtual environment and then running<syntaxhighlight lang="bash"> conda env export > environment.yml</syntaxhighlight></li></ol>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Then you can share the <code>environment.yml</code> file to another computer, and with that computer create a copy of the environment via&nbsp; &nbsp;<code data-lang="bash">conda env create -f environment.yml</code>

More guidance can be found here: [https://conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#sharing-an-environment conda.io]