Conda activation does not work in Terminal

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 https://github.com/microsoft/vscode-python/issues/5344 Upstream issue https://github.com/microsoft/vscode/issues/70248

[siriusmax]

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

[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.