Use conda init
As pointed out in a different answer, manually adding Conda on $PATH
is no longer recommended as of v4.4.0 (see Release Notes). Furthermore, since Conda v4.6 new functionality to manage shell initialization via the conda init
command was introduced. Hence, the updated recommendation is to run
Linux/UNIX and OS X before macOS v10.15 (Catalina)
./anaconda3/bin/conda init
Mac OS X v10.15 (Catalina) and later
./anaconda3/bin/conda init zsh
Windows
./anaconda3/Scripts/conda.exe init
You must launch a new shell or source your init file (e.g., source .bashrc
) for the changes to take effect.
Details. For an in-depth look at exactly what conda init
does see this answer.
Alternative shells
You may need to explicitly identify your shell to Conda. For example, if you run zsh
(Mac OS X 10.15+ default) instead of bash
then you would run
./anaconda3/bin/conda init zsh
Please see ./anaconda3/bin/conda init --help
for a comprehensive list of supported shells.
Word of Caution
I'd recommend running the above command with a --dry-run|-d
flag and a verbosity (-v
) flag, in order to see exactly what it would do. If you don't already have a Conda-managed section in your shell run commands file (e.g., .bashrc
), then this should appear like a straight-forward insertion of some new lines. If it isn't such a straightforward insertion, I'd recommend clearing any previous Conda sections from $PATH
and the relevant shell initialization files (e.g., bashrc
) first.
Again, for those interested, there is an in-depth look at how it works, in this answer.
Potential Automated Cleanup
Conda v4.6.9 introduced a --reverse
flag that automates removing the changes that are inserted by conda init
.