Activation
The activation of an environment makes all its contents available to your shell. It mainly adds target prefix subdirectories to your $PATH environment variable.
Note
activation implementation is platform dependent.
When
activating an environment from another, you can choose to
stack or not upon the currently activated env. Stacking will result in a new intermediate
prefix :
system prefix < base < env1 < env2 .
Deactivation
The deactivation is the opposite operation of activation , removing from your shell what makes the environment content accessible.
If you want to change selection, open document below and click on "Move attachment"
Concepts — documentationnts based on this base environment. Note You can’t create the base environment because it’s already part of the root prefix structure. Directly install in base instead. Activation/Deactivation# <span>Activation# The activation of an environment makes all its contents available to your shell. It mainly adds target prefix subdirectories to your $PATH environment variable. Note activation implementation is platform dependent. When activating an environment from another, you can choose to stack or not upon the currently activated env. Stacking will result in a new intermediate prefix: system prefix < base < env1 < env2. Deactivation# The deactivation is the opposite operation of activation, removing from your shell what makes the environment content accessible. previous Micromamba Installation next Mamba User Guide Contents Prefix/Environment Root prefix Base environment Activation/Deactivation Activation Deactivation By QuantStack & mamba Summary
| status | not read | | reprioritisations | |
|---|
| last reprioritisation on | | | suggested re-reading day | |
|---|
| started reading on | | | finished reading on | |
|---|
Details