condacommand available on your computer, and you can then use
condato install and update more python packages and their dependencies.
defaultchannel (or repository) provided by the conda repository. This is not very useful because we will be mostly using (the same) packages provided by the conda-forge channel.
Note: some extra details are available on the much older page Installing and maintaining UV-CDAT with conda. You can check later the Useful conda commands, but the official conda documentation and the Cheat sheet are probably more up-to-date.
By Linux-like, we mean:
wgetto download the installer:
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh(90 Mb, 26 Feb 2021)
Do you wish the installer to initialize Miniconda3 by running conda init? [yes|no]⇒ NO
/home/your_login/directory does not work. You need to accept the installation in the default location:
miniconda3directory size is 342M
> du -sh miniconda3 342M miniconda3 > cd miniconda3 > du -sh * 20M bin 0 compiler_compat 4.0K condabin 684K conda-meta 0 envs 16K etc 5.5M include 4.0K info 198M lib 12K LICENSE.txt 114M pkgs 604K share 4.0K shell 0 ssl 0 x86_64-conda_cos6-linux-gnu
condacommand, and use it to initialize the base environment
$ which conda <installation_path>/miniconda3/condabin/conda $ which python /usr/bin/python $ conda activate (base) $ which python <installation_path>/miniconda3/bin/python
$ conda update --all [...]
miniconda3directory size goes from 432 Mb to 581 Mb. This directory will keep on growing, which is the reason why you should put it on a (preferably non backed up) disk where you have enough space
condapackage (just in case we did not get it with the update)
conda update -n base conda
When you open a terminal, your shell needs to know where to find the
conda command used to initialize an environment, or switch between environments
You were asked the following question when installing miniconda3: Do you wish the installer to initialize Miniconda3 by running conda init? [yes|no]
condadirectly available when you open a new terminal
We choose not to add a
conda activate env_name line to the shell configuration files, in order to avoid side effects. When we open a new terminal, we get the default python available on the system. When we need a specific python environment, we just open a new window and then explicitly type:
conda activate env_name
In the case of python environments maintained by a single user, but used by several users, we could do the same as in the General case, but it can be useful to have the users source an intermediate initialization file, that will then source the initialization file used in the general case. This makes it easier to maintain and change the environments, without asking users to make changes.
.conda3_jyp.shfile looking like conda3_jyp.sh.txt
.conda3_jyp.cshfile looking like conda3_jyp.csh.txt
conda will probably work fine with the default settings for creating new environments with just one package (e.g. just PyFerret).
We intend to create complex environments (combining lots of packages, with complex dependencies) and it is highly recommended to use the specific settings described in this section
conda config –show
Most of the packages we will install will be provided by the conda-forge channel (
-c conda-forge option). The installation steps will also add dependencies that will theoretically come from conda-forge, but could also come from the defaults channel.
The following will make sure that we only get packages from conda-forge unless the requested packages really don't exist on conda-forge (see Managing channels and Using multiple channels => How to fix it)
$ conda config --add channels conda-forge $ conda config --set channel_priority strict $ cat ~/.condarc channels: - conda-forge - defaults channel_priority: strict
Even when using a proper
.condarc in order to get packages coming only from conda-forge,
conda install may fail to solve the dependencies after meditating during an enormous time (e.g. Solving environment: failed with initial frozen solve. Retrying with flexible solve.), when we try to deal with complex environments (i.e. we already have lots of installed packages and we want to install even more packages).
Using CDAT as a base environment, and adding a lot of extra packages is a complex environment.