Conda activate not working

Question

gonzo     a packages   conda env list   conda environments    ppo latest                nohome jaan abhishek anaconda3 envs ppo latest root                      nohome jaan abhishek anaconda3   gonzo     a packages   conda activate ppo latest  gonzo     a packages   which python                                                                                      ppo latest   nohome jaan abhishek anaconda3 bin python  gonzo     a packages   conda deactivate                                                                                  ppo latest   gonzo     a packages   which python  nohome jaan abhishek anaconda3 bin python   The environment gets activated without an error  Then we check which python it is referring to it  It is doesn t change  why

User · Answer

To use  conda activate  via Windows CMD  not the Anaconda Prompt    in response to okorng s question  although using the Anaconda Prompt is the preferred option   First  we need to add the activate bat script to your path   Via CMD   set PATH  PATH   lt your path to anaconda installation gt  Scripts   Or via Control Panel  open  User Accounts  and choose  Change my environment variables    Then calling directly from Windows CMD   activate  lt environment name gt    without using the prefix  conda     Tested on Windows 7 Enterprise with Anaconda3-5 2 0

User · Answer

Just use this command in your cmd  activate  lt envname gt   Works like charm   worked for windows  don t know about mac

User · Answer

Here s what worked for me  using the Git Bash terminal in VS Code on windows in succinct steps    source activate env-name - You should see your line appended by the  base  tag now  After calling on source activate  I ve found following conda activate commands to work  i e  conda activate env2-name   What didn t work for Git Bash  as a VS Code terminal  for me  activate env-name and conda activate env-name   Not exactly sure why this specific behaviour occurs on the Git Bash terminal on VS Code  but the accepted answer   this stackoverflow question I ve found might provide clues

User · Answer

After installing conda in Linux if you are trying to create env just type bash and hit Enter later you can create env

User · Answer

This solution is for those users who do not want to set PATH   Sometimes setting PATH may not be desired  In my case  I had Anaconda installed and another software with a Python installation required for accessing the API  and setting PATH was creating conflicts which were difficult to resolve   Under the Anaconda directory  in this case Anaconda3  there is a subdirectory called envs where all the environments are stored  When using conda activate some-environment replace some-environment with the actual directory location of the environment   In my case the command is as follows   conda activate C  ProgramData Anaconda3 envs some-environment

User · Answer

If nothing works for you  you can specify the full path of your python environment setup by conda  For me  I set up an environment called  quot testenv quot  using conda  I searched all python environments using whereis python   grep  miniconda   It returned a list of python environments  Then I ran my python file py using the following command    miniconda3 envs testenv bin python3 8 my python file py  You can do the same thing on windows too but looking up for python and conda python environments is a bit different

User · Answer

source activate      source deactivate

User · Answer

Have you tried with Anaconda command prompt or  cmd it works for me  Giving no error and activation is not working in PowerShell may be some path issue

User · Answer

In the windows environment use  anaconda prompt  instead of  command prompt

User · Answer

For windows  Use the Anaconda Powershell Prompt

User · Answer

Functions are not exported by default to be made available in subshells  I d recommend you do  source   anaconda3 etc profile d conda sh conda activate my env  In the commands above  replace   anaconda3  with the path to your miniconda   anaconda installation

User · Answer

As of conda 4 4  the command  conda activate  lt envname gt    is the same on all platforms  The procedure to add conda to the PATH environment variable for non-Windows platforms  on Windows you should use the Anaconda Prompt   as well as the change in environment activation procedure  is detailed in the release notes for conda 4 4 0     For conda versions older than 4 4  command is either  source activate  lt envname gt    on Linux and macOS or  activate  lt envname gt    on Windows  You need to remove the conda

User · Answer

Try this   export PATH  home your username anaconda3 bin  PATH in    bashrc   Then source    bashrc This works for me for the same problem

User · Answer

The anaconda functions are not exported by default  it can be done by using the following command     source   anaconda3 etc profile d conda sh   conda activate my env

User · Answer

I just ran into a similar issue  Recently started developing on windows  so getting used to the PowerShell  Ironically when trying to use  conda activate   in Git-bash i got the error     conda activate obf  CommandNotFoundError  Your shell has not been properly configured to use  conda activate   If using  conda activate  from a batch script  change your invocation to  CALL conda bat activate    To initialize your shell  run        conda init  lt SHELL NAME gt   Currently supported shells are    - bash   - cmd exe   - fish   - tcsh   - xonsh   - zsh   - powershell  See  conda init --help  for more information and options   IMPORTANT  You may need to close and restart your shell after running  conda init      Running the command in my PowerShell  elevated  as instructed did the trick for me   conda init powershell    This should be true across all terminal environments  just strange PowerShell didn t return this error itself

User · Answer

I just created a new environment with conda and things are different  My sys path was not correct for a bit until I figured out way   As a result  I want to point out for anyone else confused by a change in conda  that if you have upgraded conda and created an environment  it will now tell you  as opposed to previous behavior      To activate this environment  use           conda activate test     To deactivate an active environment  use           conda deactivate   Thus  the new way to activate deactivate environments is to do it like the above   Indeed  if you upgrade from an older version of conda and you try the above  you may see the following helpful message  which I did    CommandNotFoundError  Your shell has not been properly configured to use  conda activate   If your shell is Bash or a Bourne variant  enable conda for the current user with        echo      anaconda etc profile d conda sh   gt  gt     bash profile  or  for all users  enable conda with        sudo ln -s   anaconda etc profile d conda sh  etc profile d conda sh  The options above will permanently enable the  conda  command  but they do NOT put conda s base  root  environment on PATH   To do so  run        conda activate  in your terminal  or to put the base environment on PATH permanently  run        echo  conda activate   gt  gt     bash profile  Previous to conda 4 4  the recommended way to activate conda was to modify PATH in your    bash profile file   You should manually remove the line that looks like      export PATH    anaconda bin  PATH       The above line should NO LONGER be in your    bash profile file        Changing the above fixed my issues with sys path in activated conda environments

User · Answer

If your console does not show  base  after running conda activate base  then try running  conda init Then running conda activate  lt your env gt  should show the name of   lt your env gt   at the beginning of the shell prompt  This worked for me on Windows  My PATH environment variable was set properly so conda activate base did not raise any error but quietly failed

[anaconda] Conda activate not working?

Examples related to anaconda

Examples related to conda