Conda activation does not work in Terminal

[DonJayamanne]

Environment data

• VS Code version: Stable/Insiders
• Extension version (available under the Extensions sidebar): N/A
• OS and version: Mac
• Python version (& distribution if applicable, e.g. Anaconda): Anaconda 4.6
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): Conda
• Relevant/affected Python packages and their versions: N/A

Expected behaviour

When a conda environment activated using conda activate xxx, then using python xxx will point to the activated environment.

Actual behaviour

Even though a conda environment has been activated, which python will point to the wrong environment.

Steps to reproduce:

1. Open terminal (without python extenions)
2. Run command conda activate xxx
3. Run command which python

Tracked here #5344
Upstream issue microsoft/vscode#70248

[djnsu]

I have exactly the same problem. Conda env activation doesnt't work from vscode, but works fine from iTerm/Terminal.

[AlexTaguchi]

I seem to be having the same problem (identical to microsoft/vscode#72188)

[DonJayamanne]

Upstream issues:

• Update default value for terminal.integrated.inheritEnv vscode#75377
• Support using a "clean" environment for the terminal vscode#70248

Also check:

• Conda initialization scripts in ~/.bash_profile are not idempotent conda/conda#8703

[Co2Link]

OS: windows10
select 'Command Prompt' as Default shell fix my problem

[siriusmax]

Same problem. Wonder how to solve it in macos

[siriusmax]

checking off the 'inherit Env' in settings solved this issue on my mac

[luabud]

@DonJayamanne would the proposed solution below work? Do you think this could cause problems for those who are not using conda?

• Check if "terminal.integrated.inheritEnv" is set on the user's user settings
• If not, then set it to false

[DonJayamanne]

Yes we can do that, however I'm tempted to do the following:

• Prompt and change the setting in user settings.json
• Ask user to exit vscode and reload it (Not sure restarting VS Code will work).

Changing settings without users consent is not something we should be doing.

would the proposed solution below work?

Yes. My suggestion is to do this ONLY when user is using conda. Not otherwise. I.e. minimize the number of users that will be impacted by this change.

Do you think this could cause problems for those who are not using conda?

Not that I'm aware of. We can find out.

[DonJayamanne]

See PR in progress #6959

[luabud]

Prescribed solution

Cool, so if it isn't a Windows machine and if the selected interpreter is a conda environment and "terminal.integrated.inheritEnv" is not set on the user's user settings, we can prompt the message below:

"We noticed you're using a conda environment. If you are experiencing issues with this environment in the integrated terminal, we suggest the "terminal.integrated.inheritEnv" setting to be changed to false. Would you like to update this setting?"
Options: Yes, No

And add telemetry for the yes selection, so we can know if this is actually solving the issue.

[luabud]

Closing in favour of #7607