Skip to content

Commit 6b4b828

Browse files
committed
update miniconda osx docs for activation steps
1 parent b806dd7 commit 6b4b828

File tree

1 file changed

+3
-22
lines changed

1 file changed

+3
-22
lines changed

docs/source/user-guide/install/macos.rst

+3-22
Original file line numberDiff line numberDiff line change
@@ -56,31 +56,12 @@ EXAMPLE:
5656
5757
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-MacOSX-x86_64.sh -O ~/miniconda.sh
5858
bash ~/miniconda.sh -b -p $HOME/miniconda
59-
export PATH="$HOME/miniconda/bin:$PATH"
59+
..
6060
61-
.. note::
62-
This sets the PATH only for the current session, not
63-
permanently. Trying to use conda when conda is not in your
64-
PATH causes errors such as "command not found."
65-
66-
In each new bash session, before using conda, set the PATH and
67-
run the activation scripts of your conda packages by running::
68-
69-
source $HOME/miniconda/bin/activate
61+
The installer prompts “Do you wish the installer to initialize Miniconda3 by running conda init?” We recommend “yes”.
7062

7163
.. note::
72-
Replace ``$HOME/miniconda/bin/activate``
73-
with the path to the activate script in your conda installation.
74-
75-
To set the PATH permanently, you can add a line to your
76-
``.bashrc`` file. However, this makes it possible to use conda
77-
without running the activation scripts of your conda packages,
78-
which may produce errors.
79-
80-
EXAMPLE::
81-
82-
export PATH="$HOME/miniconda/bin:$PATH"
83-
64+
If you enter “no”, then conda will not modify your shell scripts at all. In order to initialize after the installation process is done, first run source <path to conda>/bin/activate and then run conda init.
8465

8566
Updating Anaconda or Miniconda
8667
==============================

0 commit comments

Comments
 (0)