We Keep Coding

Is there an "activate" script in an Anaconda environment? [duplicate]

I'm on Windows 8, using Anaconda 1.7.5 64bit.
I created a new Anaconda environment with
conda create -p ./test python=2.7 pip
from C:\Pr\TEMP\venv\.
This worked well (there is a folder with a new python distribution). conda tells me to type
activate C:\PR\TEMP\venv\test
to activate the environment, however this returns:
No environment named "C:\PR\temp\venv\test" exists in C:\PR\Anaconda\envs
How can I activate the environment? What am I doing wrong?

If this happens you would need to set the PATH for your environment (so that it gets the right Python from the environment and Scripts\ on Windows).
Imagine you have created an environment called py33 by using:
conda create -n py33 python=3.3 anaconda
Here the folders are created by default in Anaconda\envs, so you need to set the PATH as:
set PATH=C:\Anaconda\envs\py33\Scripts;C:\Anaconda\envs\py33;%PATH%
Now it should work in the command window:
activate py33
The line above is the Windows equivalent to the code that normally appears in the tutorials for Mac and Linux:
$ source activate py33
More info:
https://groups.google.com/a/continuum.io/forum/#!topic/anaconda/8T8i11gO39U
Does `anaconda` create a separate PYTHONPATH variable for each new environment?

Use cmd instead of Powershell!
I spent 2 hours before I switched to cmd and then it worked!
create Environment:
conda create -n your_environment_name
see list of conda environments:
conda env list
activate your environment:
conda activate your_environment_name
That's all folks

Note that the command for activating an environment has changed in Conda version 4.4. The recommended way of activating an environment is now conda activate myenv instead of source activate myenv. To enable the new syntax, you should modify your .bashrc file. The line that currently reads something like
export PATH="<path_to_your_conda_install>/bin:$PATH"
Should be changed to
. <path_to_your_conda_install>/etc/profile.d/conda.sh
This only adds the conda command to the path, but does not yet activate the base environment (which was previously called root). To do also that, add another line
conda activate base
after the first command. See all the details in Anaconda's blog post from December 2017. (I think that this page is currently missing a newline between the two lines, it says .../conda.shconda activate base).
(This answer is valid for Linux, but it might be relevant for Windows and Mac as well)

All the former answers seem to be outdated.
conda activate was introduced in conda 4.4 and 4.6.
conda activate: The logic and mechanisms underlying environment activation have been reworked. With conda 4.4, conda activate and conda deactivate are now the preferred commands for activating and deactivating environments. You’ll find they are much more snappy than the source activate and source deactivate commands from previous conda versions. The conda activate command also has advantages of (1) being universal across all OSes, shells, and platforms, and (2) not having path collisions with scripts from other packages like python virtualenv’s activate script.
Examples
conda create -n venv-name python=3.6
conda activate -n venv-name
conda deactivate
These new sub-commands are available in "Aanconda Prompt" and "Anaconda Powershell Prompt" automatically. To use conda activate in every shell (normal cmd.exe and powershell), check expose conda command in every shell on Windows.
References
How to Get Ready for the Release of conda 4.4
Conda 4.6 Release

As you can see from the error message the paths, that you specified, are wrong. Try it like this:
activate ..\..\temp\venv\test
However, when I needed to install Anaconda, I downloaded it from here and installed it to the default paths (C:\Anaconda), than I put this path to the environment variables, so now Anacondas interpreter is used as default. If you are using PyCharm, for example, you can specify the interpreter there directly.

I've tried to activate env from Jenkins job (in bash) with
conda activate base and it failed, so after many tries, this one worked for me (CentOS 7) :
source /opt/anaconda2/bin/activate base

Below is how it worked for me
C:\Windows\system32>set CONDA_ENVS_PATH=d:\your\location
C:\Windows\system32>conda info
Shows new environment path
C:\Windows\system32>conda create -n YourNewEnvironment --clone=root
Clones default root environment
C:\Windows\system32>activate YourNewEnvironment
Deactivating environment "d:\YourDefaultAnaconda3"...
Activating environment "d:\your\location\YourNewEnvironment"...
[YourNewEnvironment] C:\Windows\system32>conda info -e
conda environments:
#
YourNewEnvironment
* d:\your\location\YourNewEnvironment
root d:\YourDefaultAnaconda3

Though #Simba had a good answer at the time, a lot has changed in the conda env since 4.6. Conda activate (env-name) overthrew source activate (env-name) for good but not without it own challenges. conda activate oftentimes forces your environment to base and makes you see something like this:
and throwing loads of error back at you. This can also be because auto_activate_base is set to True.
You can check this by using the following command
conda config --set auto_activate_base False
source ~/.bashrc
And to reactivate use this
conda config --set auto_activate_base True
source ~/.bashrc

let's assume your environment name is 'demo' and you are using anaconda and want to create a virtual environment:
(if you want python3)
conda create -n demo python=3
(if you want python2)
conda create -n demo python=2
After running above command you have to activate the environment by bellow command:
source activate demo

For me, using Anaconda Prompt instead of cmd or PowerShell is the key.
In Anaconda Prompt, all I need to do is activate XXX

I was having the same, a fix seems to have been made in the source.

One special case: If you are trying to put the activation command in a unix script, you might run into a problem because when you run the bash script, a new (linux) shell environment is created, and then destroyed when you exit that script. Think of this as running bash, then source activate... / conda activate..., then running exit to exit that shell... The result is you end up without an activated shell... More details in How to execute script in the current shell on Linux?:
TL;DR: for linux, to activate in a bash script and leave active:
Add the line #!/bin/bash as the first line of the script (This is anyways always a good practice, it specifies this is a bash script)
Type the command source shell_script.sh or . shell_script.sh
Note: . in bash is equivalent to source in bash.

I'm using conda with Windows 10.
Anaconda was installed in:
C:\User\Admin\Anaconda3
After installation I've added this folders to system PATH:
C:\User\Admin\Anaconda3
C:\User\Admin\Anaconda3\Scripts
Then I ran "Anaconda promt" from windows start menu. From this anaconda promt I created my environment with
conda create --name my_env
And after that, I'm able to activate my conda environment from regular CMD by just typing:
activate my_env

For me running this works in VS Code:
C:/ProgramData/Anaconda3/Scripts/activate
Or just creating a new Terminal.

Window:
conda activate environment_name
Mac: conda activate environment_name

Windows CMD: "This Python interpreter is in a conda environment, but the environment has not been activated"

I am trying to run Anaconda Python in a command prompt. However, when I do, I get:
This Python interpreter is in a conda environment, but the environment
has not been activated. Libraries may fail to load. To activate this
environment please see https://conda.io/activation
I have tried to run
conda base activate
and
<path to Anaconda>\Scripts\activate base
from within the Windows command prompt and it does nothing. How can I fix this?

You should have a look at the Anaconda documentation. If you want to activate the "base" environment, you should just type:
conda activate
However, it is usually better to create a virtual environment first, like this:
conda create -n myTestEnv
And in order to activate it, now write:
conda activate myTestEnv
To check the environments that you currently have on your machine you can type conda env list in the Terminal.

Activating conda environment with its full path

Usually, we activate a conda environment with the command:
source activate env_name
Is it possible to activate conda environment with its full path? For example:
source (fullpath)/bin/activate
When I do this it activates the default environment of anaconda i.e the root environment.

Update for conda 4.4 and up:
You need to specify the conda environment path to activate. The new conda activate command should not need the full path to an "activate script" any longer, since the command is now "built-in" to conda. So something like:
conda activate (fullpath)/env-name-here
should work.
The command you have specified activates the root environment because you have not given conda an environment to activate, and root is the default. If you want to activate a particular environment, you can certainly do so with the full path to the activate script, for instance
source (full path to main Anaconda directory)/bin/activate (fullpath)/env-name-here
^^^^^^^^^^^^^^^^^^^^^^^^
You're missing this part

You can activate an environment that is not in your conda environment list by passing the path to the environment. For example you can create an environment in any directory you want with the -p argument. Like so:
conda create -p /path/to/some/location/mytestenv/ python=3.5
This will NOT show up in conda env list, but you can activate it with:
source activate /path/to/some/location/mytestenv

yes, it does activates the default environment of anaconda.
you can see the list of created or available environments by :
conda env list
don't understand, what was the answer you were looking for ?

Sure, this is a old question but writing the answer for folks returning to this page. When you create a conda environment with the prefix, you'll not be allowed to give it a name. Please follow the below steps so that you'll have name for your conda environment and can activate it directly by using the name rather than the full path.
Navigate to the custom folder where you want to create the new environment.
D:\condaEnvs>conda create --prefix=FastAI --> This creates a conda environment named FastAI
D:\condaEnvs> conda config --append envs_dirs ‘D:\condaEnvs\FastAIEnv’ --> This will give a name to your newly created conda environment.
With the new versions of conda, we dont have this issue anymore.

having default Mac Python 2.7 and Anaconda Python 3

I want to keep the Mac Python as my main 'python'. The reason for that is the recommendation in Python website here. I also want to add a separate environment for my Python3 (Anaconda).
For doing that I installed the Anaconda Python to get access to Conda and then I made an environment for my Python3 using the following command:
conda create -n py36 python=3.6 anaconda
When I installed the Anaconda python it added this to my .bash_profile file to get access to all conda commands:
# added by Anaconda3 4.4.0 installer
# export PATH="/Users/omidb/anaconda/bin:$PATH"
Now my default python is anaconda python which I don't want to.
How can I have default Mac python as my main python and then when I needed Anaconda, just use source activate py36 ?

UPDATED ANSWER
After testing this, I feel it's appropriate to offer this as a simple solution for using Mac Python as the default and only using Conda Python when desired.
You need to add/move the conda path to the end of your PATH environment via export command. This should allow you to use the Mac Python as the default and only use Anaconda Python after calling source activate py36.
export PATH="$PATH:/Users/omidb/anaconda/bin"
Path Resolution
This solution assumes you have /usr/bin/ (where Mac Python is) already in your PATH. Resolution order should check that directory first assuming it's first in the PATH. Also, this setup does not require symlinks in /usr/local/bin. I am not a fan of manipulating system-level resources for solutions that can be done with user resources (directories).
Default Python Setup
After moving the Anaconda path to the end of your PATH environment variable, you can validate that which python references /usr/bin/python, the location for Mac Python. You will run Mac python by default at the command line.
Running Conda Python
As previously noted, you have to call source activate py36 when you want to use the conda virtual environment. There is no need for adding symlinks to /usr/local/bin as they are already available through ~/anaconda/bin/.
Furthermore, source activate py36 (or any other Anaconda environment), it will add the appropriate environment path for Anaconda python to the beginning of your PATH environment variable, which (referring back to Path Resolution) would be executed when run as python on the command line. You can validate this with which python after running source activate py36. conda also stores the previous path as the environment variable CONDA_PATH_BACKUP.
Deactivating Conda
After running source deactivate, the original path is restored, so you will then be back to running Mac python.

Faced the same problem and question is too old but the simplest of doing this which I found is:
1. Let's check if the default python version is pointing to Conda python
which python - If Conda installation updated to your bashrc or zshrc, it will show that path
Running Command:
conda config --set auto_activate_base false
It's will make sure that when you start the terminal, Conda doesn't get activated as base
Now if you check python --version or which python - It should be pointing to mac default python version
Now whenever you want to use conda, all conda commands are available with conda <command>
Create the virtual env using conda create --name venv and activate it using conda activate <venv_name>
Now, I am able to use different python versions I required with conda and default python version as system default

How to activate an Anaconda environment

I'm on Windows 8, using Anaconda 1.7.5 64bit.
I created a new Anaconda environment with
conda create -p ./test python=2.7 pip
from C:\Pr\TEMP\venv\.
This worked well (there is a folder with a new python distribution). conda tells me to type
activate C:\PR\TEMP\venv\test
to activate the environment, however this returns:
No environment named "C:\PR\temp\venv\test" exists in C:\PR\Anaconda\envs
How can I activate the environment? What am I doing wrong?

If this happens you would need to set the PATH for your environment (so that it gets the right Python from the environment and Scripts\ on Windows).
Imagine you have created an environment called py33 by using:
conda create -n py33 python=3.3 anaconda
Here the folders are created by default in Anaconda\envs, so you need to set the PATH as:
set PATH=C:\Anaconda\envs\py33\Scripts;C:\Anaconda\envs\py33;%PATH%
Now it should work in the command window:
activate py33
The line above is the Windows equivalent to the code that normally appears in the tutorials for Mac and Linux:
$ source activate py33
More info:
https://groups.google.com/a/continuum.io/forum/#!topic/anaconda/8T8i11gO39U
Does `anaconda` create a separate PYTHONPATH variable for each new environment?

Use cmd instead of Powershell!
I spent 2 hours before I switched to cmd and then it worked!
create Environment:
conda create -n your_environment_name
see list of conda environments:
conda env list
activate your environment:
conda activate your_environment_name
That's all folks

Note that the command for activating an environment has changed in Conda version 4.4. The recommended way of activating an environment is now conda activate myenv instead of source activate myenv. To enable the new syntax, you should modify your .bashrc file. The line that currently reads something like
export PATH="<path_to_your_conda_install>/bin:$PATH"
Should be changed to
. <path_to_your_conda_install>/etc/profile.d/conda.sh
This only adds the conda command to the path, but does not yet activate the base environment (which was previously called root). To do also that, add another line
conda activate base
after the first command. See all the details in Anaconda's blog post from December 2017. (I think that this page is currently missing a newline between the two lines, it says .../conda.shconda activate base).
(This answer is valid for Linux, but it might be relevant for Windows and Mac as well)

All the former answers seem to be outdated.
conda activate was introduced in conda 4.4 and 4.6.
conda activate: The logic and mechanisms underlying environment activation have been reworked. With conda 4.4, conda activate and conda deactivate are now the preferred commands for activating and deactivating environments. You’ll find they are much more snappy than the source activate and source deactivate commands from previous conda versions. The conda activate command also has advantages of (1) being universal across all OSes, shells, and platforms, and (2) not having path collisions with scripts from other packages like python virtualenv’s activate script.
Examples
conda create -n venv-name python=3.6
conda activate -n venv-name
conda deactivate
These new sub-commands are available in "Aanconda Prompt" and "Anaconda Powershell Prompt" automatically. To use conda activate in every shell (normal cmd.exe and powershell), check expose conda command in every shell on Windows.
References
How to Get Ready for the Release of conda 4.4
Conda 4.6 Release

As you can see from the error message the paths, that you specified, are wrong. Try it like this:
activate ..\..\temp\venv\test
However, when I needed to install Anaconda, I downloaded it from here and installed it to the default paths (C:\Anaconda), than I put this path to the environment variables, so now Anacondas interpreter is used as default. If you are using PyCharm, for example, you can specify the interpreter there directly.

I've tried to activate env from Jenkins job (in bash) with
conda activate base and it failed, so after many tries, this one worked for me (CentOS 7) :
source /opt/anaconda2/bin/activate base

Below is how it worked for me
C:\Windows\system32>set CONDA_ENVS_PATH=d:\your\location
C:\Windows\system32>conda info
Shows new environment path
C:\Windows\system32>conda create -n YourNewEnvironment --clone=root
Clones default root environment
C:\Windows\system32>activate YourNewEnvironment
Deactivating environment "d:\YourDefaultAnaconda3"...
Activating environment "d:\your\location\YourNewEnvironment"...
[YourNewEnvironment] C:\Windows\system32>conda info -e
conda environments:
#
YourNewEnvironment
* d:\your\location\YourNewEnvironment
root d:\YourDefaultAnaconda3

Though #Simba had a good answer at the time, a lot has changed in the conda env since 4.6. Conda activate (env-name) overthrew source activate (env-name) for good but not without it own challenges. conda activate oftentimes forces your environment to base and makes you see something like this:
and throwing loads of error back at you. This can also be because auto_activate_base is set to True.
You can check this by using the following command
conda config --set auto_activate_base False
source ~/.bashrc
And to reactivate use this
conda config --set auto_activate_base True
source ~/.bashrc

let's assume your environment name is 'demo' and you are using anaconda and want to create a virtual environment:
(if you want python3)
conda create -n demo python=3
(if you want python2)
conda create -n demo python=2
After running above command you have to activate the environment by bellow command:
source activate demo

For me, using Anaconda Prompt instead of cmd or PowerShell is the key.
In Anaconda Prompt, all I need to do is activate XXX

I was having the same, a fix seems to have been made in the source.

One special case: If you are trying to put the activation command in a unix script, you might run into a problem because when you run the bash script, a new (linux) shell environment is created, and then destroyed when you exit that script. Think of this as running bash, then source activate... / conda activate..., then running exit to exit that shell... The result is you end up without an activated shell... More details in How to execute script in the current shell on Linux?:
TL;DR: for linux, to activate in a bash script and leave active:
Add the line #!/bin/bash as the first line of the script (This is anyways always a good practice, it specifies this is a bash script)
Type the command source shell_script.sh or . shell_script.sh
Note: . in bash is equivalent to source in bash.

I'm using conda with Windows 10.
Anaconda was installed in:
C:\User\Admin\Anaconda3
After installation I've added this folders to system PATH:
C:\User\Admin\Anaconda3
C:\User\Admin\Anaconda3\Scripts
Then I ran "Anaconda promt" from windows start menu. From this anaconda promt I created my environment with
conda create --name my_env
And after that, I'm able to activate my conda environment from regular CMD by just typing:
activate my_env

For me running this works in VS Code:
C:/ProgramData/Anaconda3/Scripts/activate
Or just creating a new Terminal.

Window:
conda activate environment_name
Mac: conda activate environment_name