vscode activates conda but points to the default python

[Casyfill]

Environment data

• VS Code version: 1.31.1 (1.31.1)
• Extension version (available under the Extensions sidebar): 2019.1.0
• OS and version: MacOS 10.14.3 (18D42)
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.6, conda 4.6.4
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda

Expected behavior

when conda activate env, anaconda's python is used. this works in the shell terminal

Actual behavior

when conda activate env, terminal states that env is activated - prints (env) at the beginning of the line. Same with the interpreter - VScode sees it and I am able to select it.

However, which python points to the default python on MacOS, and therefore none python 3.6-dependent packages work. Same with the interpreter - VScode fails to find packages which are installed in the env

Steps to reproduce:

1. conda env create -n py36 python=3.6 luigi
2. conda activate py36
3. which python // in vscode terminal

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

___________________ ERROR collecting tests/test_reporter.py ____________________
ImportError while importing test module '/Users/philippk/Dropbox/se_projects/4_Automation/SERJ/tests/test_reporter.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
test_reporter.py:5: in <module>
    from SE.areas import get_all_areas
E   ModuleNotFoundError: No module named 'SE'
!!!!!!!!!!!!!!!!!!! Interrupted: 3 errors during collection !!!!!!!!!!!!!!!!!!!!

PROBLEMS similarly complains about lack of packages installed and type hints.

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

(base) ZG00021:SERJ philippk$ conda activate py36
(py36) ZG00021:SERJ philippk$ which python
/usr/local/bin/python
(py36) ZG00021:SERJ philippk$ conda --version
conda 4.6.4

[karrtikr]

We don't control how conda handles activation of python. Please file an issue with conda.

[benlindsay]

If this problem is the same as my problem in #4436, then I don't think it's a conda issue. Notice that when I open iterm2 and manually run the exact same commands that VSCode appears to be running (source /Users/benlindsay/miniconda/bin/activate and conda activate ads) , everything works as expected. My PATH only gets messed up with the automatic conda activation.

On that note, @Casyfill, could you print the results of echo $PATH after the failed conda activation? I'm curious to see if you also have duplicate paths in front of path to your environment's bin directory.

[praenubilus]

Having the same problem with recent update. And I think the reason maybe how vscode handle shell initialization in Mac. So if you open a terminal outside of VSCode, the $PATH will be set by following initial script from anaconda in your bash_profile or zshrc(if you are using zsh).
export PATH="/Users/xxx/anaconda3/bin:$PATH"
After that, if you do a echo $PATH, you will see value similar as following:
/Users/xxx/anaconda3/bin:/Users/xxx/anaconda3/condabin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin

However, when you fire up vscode, for some reason, the anaconda PATH has been APPENDED to system default PATH, not PREPEND. Check with echo $PATH in vscode terminal, you will see path similar as following:
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/xxx/anaconda3/bin:/Users/xxx/anaconda3/condabin
It appeared in recent vscode version, but I'm not sure if it starts from 1.31.1 on Mac.

The terminal command python will match the first executable python it found in the PATH, in vscode, it will find the default system one based on PATH value.

[praenubilus]

I've found the similar problem in another old issue #46693

[praenubilus]

Find some dark magic for workaround. In case someone with the same problem need a solution. As long as you ADD some stuff to configuration, terminal.integrated.env.osx, the content will be appended to PATH after shell initialization(source bash_profile or zshrc). In my Mojave, I simply add following empty entry to my user configuration:

"terminal.integrated.env.osx": {
		"PATH": ""
}

Then the $PATH will be the same as the external terminal.

Too busy to dive into the source code to check the root cause, maybe do it later when I have more time.

[benlindsay]

@praenubilus Thanks for the workaround! Worked like a charm.