Skip to content

Commit 190dfa8

Browse files
authored
Update env.md
1 parent f5e0ee3 commit 190dfa8

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

bash/env.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,18 @@
55

66
# environments
77

8+
There are good instructions online for installing various Python distributions. Here I am avoiding the full-blown `Anaconda`
9+
in favor of `Miniconda`; but there are other options such as `Micromamba` that run faster.
10+
11+
12+
The environment command associated with Anaconda/Miniconda is [`conda`](https://en.wikipedia.org/wiki/Conda_(package_manager))
13+
which is both an open source package and environment management system and the eponymous utility command. It is an alternative
14+
or complement to the Python native package manager `pip` (which does not manage environments).
15+
Both `pip` and `conda` can be used to install packages individually or *en masse* by means of grocery list files:
16+
`conda env create -f environment.yml` file. The corresponding environment
17+
configuration file for `pip` is called `requirements.txt`. The bulk install command using `pip` is `pip install -r requirements.txt`
18+
and the corresponding command for `conda` is
19+
820
`conda create/activate` commands -- as well as `venv` paths -- engage Python environments as augmented / customized versions
921
of the default or *base* environment. This avoids burdening the base environment with every installed Python package ever grabbed:
1022
The kitchen sink approach will become overburdened and buggy from version incompatibility issues.

0 commit comments

Comments
 (0)