| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
| conda [2020/07/17 08:36] – [Creating an environment] jansen | conda [2020/07/17 13:32] – [Installing packages] jansen |
|---|
| |
| ===== Setup ===== | ===== Setup ===== |
| Now that you have the ''conda'' package manager available, you can use it to complete the setup. | Now that you have the ''conda'' package manager available, you can use it to complete the setup. |
| | One bit of setup that ''conda'' insists on, is to add some initialization code to the login environment, so conda will always be active (''conda init bash'' or ''conda init tcsh''). However, see "pitfalls" section below. |
| | |
| | Other bits of setup can be done through the ''conda config'' commands, see ''conda config --help'' for details. It is also possible to edit the ''$HOME/.condarc'' directly if you know what settings you want (eg by looking them up online). |
| ===== Creating an environment ===== | ===== Creating an environment ===== |
| To create an environment called ''TEST'', you run | To create an environment called ''TEST'', you run |
| |
| ===== Installing packages ===== | ===== Installing packages ===== |
| | Install a package using ''conda install packagename'', optionally with a version as in ''conda install python==3.7'' to make sure that exact version gets installed, if available. |
| | |
| | If unsure what packages are available, use ''conda search packagename'' to search for any matching names (wildcards allowed, should be enclosed in quotes). To list installed packages, use ''conda list''. |
| ===== Pitfalls ===== | ===== Pitfalls ===== |
| As you can see above, the default behaviour when installing conda or running ''conda init'' is, to add some code to your .bashrc or .tcshrc to activate conda on every shell and in every window you open. That may sound like a nice feature, until you realize, that a custom version of python with a custom set of packages may wreak havoc on any environment that relies on the system default version. And there is a lot of software that happens to be written in python, or linked with it, including big parts of the Gnome and Cinnamon desktop applications. So, if you happen to set up a non-standard version of python as default, it might not be possible for you to log in in these desktop environments any more. Or even worse, if you need to install non-standard versions of gcc or its libraries, you might not be able to run a big part of the system software any more. | As you can see above, the default behaviour when installing conda or running ''conda init'' is, to add some code to your .bashrc or .tcshrc to activate conda on every shell and in every window you open. That may sound like a nice feature, until you realize, that a custom version of python with a custom set of packages may wreak havoc on any environment that relies on the system default version. And there is a lot of software that happens to be written in python, or linked with it, including big parts of the Gnome and Cinnamon desktop applications. So, if you happen to set up a non-standard version of python as default, it might not be possible for you to log in in these desktop environments any more. Or even worse, if you need to install non-standard versions of gcc or its libraries, you might not be able to run a big part of the system software any more. |
