You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noted the following questions asked during the first run...
Can you activate one environment from another or do you have to deactivatie?
Yes you can, so you can...
conda create --name python310-env python=3.10
conda create --name python39-env python=3.9
conda activate python310
conda activate python39 # Activate python39 from python310
conda deactivate # Deactivates python39 returning to python310
conda deactivate # Deactivates python310 returing to base
Can you install packages under one environment whilst another is active?
Yes, you can the default target environment is that which is active, but if you specify conda install --name then the installation will be made in the target environment.
Is there a way to set the default environment?
For OSX/Linux this can be achieved by modifying your ~/.bashrc / ~/.zshrc to run conda activate <env_name> to activate the environment you wish to always use.
For Windows its a bit more involved, there are some solutions in this thread.
Why does it take so long to resolve dependencies?
Its just the time it takes to work out what versions work with each other. This is a common complaint/question for some time and a newer, faster package manager is available called mamba which is considerably faster.
The text was updated successfully, but these errors were encountered:
Noted the following questions asked during the first run...
Can you activate one environment from another or do you have to deactivatie?
Yes you can, so you can...
Can you install packages under one environment whilst another is active?
Yes, you can the default target environment is that which is active, but if you specify
conda install --name
then the installation will be made in the target environment.Is there a way to set the default environment?
For OSX/Linux this can be achieved by modifying your
~/.bashrc
/~/.zshrc
to runconda activate <env_name>
to activate the environment you wish to always use.For Windows its a bit more involved, there are some solutions in this thread.
Why does it take so long to resolve dependencies?
Its just the time it takes to work out what versions work with each other. This is a common complaint/question for some time and a newer, faster package manager is available called mamba which is considerably faster.
The text was updated successfully, but these errors were encountered: