Initialize conda for shell interaction.
usage: conda init [-h] [--all] [--user] [--no-user] [--system] [--reverse] [--json] [-v] [-q] [-d] [SHELLS ...]
Possible choices: bash, fish, tcsh, xonsh, zsh, powershell
One or more shells to be initialized. If not given, the default value is 'bash' on unix and 'cmd.exe' & 'powershell' on Windows. Use the '--all' flag to initialize all shells. Available shells: ['bash', 'fish', 'powershell', 'tcsh', 'xonsh', 'zsh']
Initialize all currently available shells.
- -d, --dry-run
Only display what would have been done.
Initialize conda for the current user (default).
Don't initialize conda for the current user.
Initialize conda for all users on the system.
Undo effects of last conda init.
Output, Prompt, and Flow Control Options#
Report all output as json. Suitable for using conda programmatically.
- -v, --verbose
Can be used multiple times. Once for detailed output, twice for INFO logging, thrice for DEBUG logging, four times for TRACE logging.
- -q, --quiet
Do not display progress bar.
Key parts of conda's functionality require that it interact directly with the shell within which conda is being invoked. The conda activate and conda deactivate commands specifically are shell-level commands. That is, they affect the state (e.g. environment variables) of the shell context being interacted with. Other core commands, like conda create and conda install, also necessarily interact with the shell environment. They're therefore implemented in ways specific to each shell. Each shell must be configured to make use of them.
This command makes changes to your system that are specific and customized for each shell. To see the specific files and locations on your system that will be affected before, use the '--dry-run' flag. To see the exact changes that are being or will be made to each location, use the '--verbose' flag.
IMPORTANT: After running conda init, most shells will need to be closed and restarted for changes to take effect.