Activating a conda environment using conda instead of source

[eyadsibai]

Environment data

• VS Code version: 1.23.1
• Extension version (available under the Extensions sidebar): 2018.5.0
• OS and version: Linux Manjaro 4.16.13-1
• Python version (& distribution if applicable, e.g. Anaconda): 3.6.3 / conda version: 4.5.2
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda

Actual behavior

I am using the zsh shell. When I create a new python terminal it uses source activate 'name_of_environment'

Expected behavior

I am using the zsh shell. When I create a new python terminal it uses conda activate 'name_of_environment

Steps to reproduce:

1. install latest conda
2. add ". /etc/profile.d/conda.sh" to your .zshrc file as recommended by any conda version after 4.4
3. try to create a new python terminal within vscode whille the activateEnviroment setting is true

[DonJayamanne]

Further info can be found here:

conda/conda#6639

https://github.com/conda/conda/blob/a4c4feae404b2b378e106bd25f62cc8be15c768f/CHANGELOG.md#440-2017-12-20

[brettcannon]

Re-classifying as an enhancement since the old ways still work, they have simply introduced a new way of doing this.

[eyadsibai]

the old way doesn't work for me. If I am following the new way of adding the conda to the environment, the old way doesn't work anymore.

I am getting an error:
source: no such file or directory: activate

[brettcannon]

Anaconda's shell scripts that they have you source as part of the new approach must be clobbering something then.

The problem is that we can't leave old users behind and blindly cut over to this new approach, so if we're going to support both we are going to have to add detection code for what version of Anaconda someone is using which complicates things.

[brettcannon]

@eyadsibai BTW, if you need to shut off our automatic activation then see https://code.visualstudio.com/docs/python/environments#_activate-an-environment-in-the-terminal for the python.terminal.activateEnvironment.

[brettcannon]

Another snafu in all of this is that this new approach is only documented for UNIX-based operating systems and not for Windows at all.

[eyadsibai]

@brettcannon thanks, but I like that feature 😅 , I hope it can be resolved soon.
Why dont u assume one approach and if you get an error you try the other one. Similar when trying to install a package using conda. you try to source the environment if it doesn't work you try to install the package thru the conda command without sourcing the environment. Similar approach can be done here.

[brettcannon]

@eyadsibai it's not that simple because we don't have that kind of access to the terminal, i.e. we just get to send in text to execute and that's pretty much it. So we will have to do detection on the TypeScript side of things to figure out the right approach.

Could you do us a favour and let us know if executing that shell script multiple times causes an issue? E.g. if we blindly executed it and then the conda activate command would it work as appropriate?

[brettcannon]

It looks like this approach is entirely for UNIX only; Windows is still only for Command Prompt and still through the activate.bat script (at least to activate the base environment, and then conda activate is available).

[brettcannon]

And final comment: conda has not updated their docs on activating an environment yet.

[ericsnowcurrently]

@brettcannon, is there anything left to "verify" here?

[brettcannon]

@ericsnowcurrently yep, it was to verify that if you follow conda's current documentation does it break our approach to conda environment activation (i.e. does adding the recommended stuff to your shell break us).

[d3r3kk]

Adding the recommended stuff to your shell does not break us, but it doesn't always work, either. See issue #2315 and #2266 for further efforts being put toward this issue.

Closing this issue as it is covered by others.

[DonJayamanne]

@d3r3kk

I'd close #2315 and keep this open, as this has the original issue and the solution. (I.e. mentioned the new way of activation). #2315 merely mentioned another symptom.

[ericsnowcurrently]

BTW, I tried out miniconda 4.4.0+ on Windows and it worked fine. So we don't need to change anything there.

[DonJayamanne]

I'm assuming this is with mini-conda not being in path.

[ericsnowcurrently]

correct

[DonJayamanne]

I'm creating an issue for Windows + Conda

[DonJayamanne]

@ericsnowcurrently
This has never worked for @jmew, and that's why we pulled this issue into this sprint.
I've created an issue to resolve/track this #2753

[DonJayamanne]

Fails on a Mac

[DonJayamanne]

I modified the code, and found that it still fails.
When attempting to activate in 4.5.11, i get the following message:

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 ". /Users/donjayamanne/anaconda3/etc/profile.d/conda.sh" >> ~/.bash_profile

or, for all users, enable conda with

    $ sudo ln -s /Users/donjayamanne/anaconda3/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" >> ~/.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="/Users/donjayamanne/anaconda3/bin:$PATH"

^^^ The above line should NO LONGER be in your ~/.bash_profile file! ^^^

Next, I re-enabled the above in my bash_profile.
And it still fails.

I.e. for 4.4.0, I think we should NOT use the fully qualified path, we have to get the user to add the necessary startup script into their bash_profile.
I'd expect the same to be on linux as well.

@ericsnowcurrently
Please could you confirm, the behavior on Linux (I'm assuming that's where you're testing this).

@brettcannon /cc

We might have to review the solution for Mac & Linux.
Windows has been (is being) sorted in a separate issue.

[ericsnowcurrently]

We are going to try going back to source activate but with an absolute path to the "activate" script based on the path to conda.

[mdivk]

cat /opt/cloudera/parcels/Anaconda/etc/profile.d/conda.sh

_CONDA_EXE="/home/jhelmus/workspace/misc/cdh_parcel/anaconda/scripts/parcel/tmp/Anaconda-5.1.0/bin/conda"
_CONDA_ROOT="/home/jhelmus/workspace/misc/cdh_parcel/anaconda/scripts/parcel/tmp/Anaconda-5.1.0"
_conda_set_vars() {

Should Helmus folder be created for everyone using Anaconda? I am very curious on this.

[mdivk]

I am not able to activate the new env. I am using conda 4.4.10

I am using command: conda activate
Error:

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 ". /opt/cloudera/parcels/Anaconda/etc/profile.d/conda.sh" >> ~/.bashrc

or, for all users, enable conda with

$ sudo ln -s /opt/cloudera/parcels/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" >> ~/.bashrc

Previous to conda 4.4, the recommended way to activate conda was to modify PATH in
your ~/.bashrc file. You should manually remove the line that looks like

export PATH="/opt/cloudera/parcels/Anaconda/bin:$PATH"

^^^ The above line should NO LONGER be in your ~/.bashrc file! ^^^

[hadoopuser@hadoop02 bin]$ conda activate py36

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 ". /opt/cloudera/parcels/Anaconda/etc/profile.d/conda.sh" >> ~/.bashrc

or, for all users, enable conda with

$ sudo ln -s /opt/cloudera/parcels/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" >> ~/.bashrc

Previous to conda 4.4, the recommended way to activate conda was to modify PATH in
your ~/.bashrc file. You should manually remove the line that looks like

export PATH="/opt/cloudera/parcels/Anaconda/bin:$PATH"

^^^ The above line should NO LONGER be in your ~/.bashrc file! ^^^

If I followed the instruction in the above error output, I got new error prompted in the output below:

-bash: /home/jhelmus/workspace/misc/cdh_parcel/anaconda/scripts/parcel/tmp/Anaconda-5.1.0/bin/conda: No such file or directory

So what it the secret command to activate an environment? My Anaconda is 4.4.Thank you very much.

[DonJayamanne]

If I followed the instruction in the above error output, I got new error prompted in the output below:
-bash: /home/jhelmus/workspace/misc/cdh_parcel/anaconda/scripts/parcel/tmp/Anaconda-5.1.0/bin/conda: No such file or directory

So what it the secret command to activate an environment?

Please file your issue against conda, they'll be able to assist you with your issue.