Translations:Anaconda/28/en: Difference between revisions
Jump to navigation
Jump to search
(fix typo) |
No edit summary |
||
Line 1: | Line 1: | ||
* Anaconda very often installs software (compilers, scientific libraries etc.) which already exist on | * Anaconda very often installs software (compilers, scientific libraries etc.) which already exist on our clusters as modules, with a configuration that is not optimal. | ||
* It installs binaries which are not optimized for the processor architecture on our clusters. | * It installs binaries which are not optimized for the processor architecture on our clusters. | ||
* It makes incorrect assumptions about the location of various system libraries. | * It makes incorrect assumptions about the location of various system libraries. |
Latest revision as of 12:56, 13 September 2022
- Anaconda very often installs software (compilers, scientific libraries etc.) which already exist on our clusters as modules, with a configuration that is not optimal.
- It installs binaries which are not optimized for the processor architecture on our clusters.
- It makes incorrect assumptions about the location of various system libraries.
- Anaconda uses the $HOME directory for its installation, where it writes an enormous number of files. A single Anaconda installation can easily absorb almost half of your quota for the number of files in your home directory.
- Anaconda is slower than the installation of packages via Python wheels.
- Anaconda modifies the $HOME/.bashrc file, which can easily cause conflicts.