Repository navigation
Conda activation does not work in Terminal #5764
Description
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:
- Open terminal (without python extenions)
- Run command
conda activate xxx - Run command
which python
Tracked here #5344
Upstream issue microsoft/vscode#70248
Activity
[-]Even though conda env is activated `python` points to default `python` interpreter[/-][+]Conda activation does not work in Terminal[/+]djnsu commentedon Jun 4, 2019
I have exactly the same problem. Conda env activation doesnt't work from vscode, but works fine from iTerm/Terminal.
AlexTaguchi commentedon Jun 5, 2019
I seem to be having the same problem (identical to microsoft/vscode#72188)
DonJayamanne commentedon Jun 13, 2019
Upstream issues:
Also check:
~/.bash_profileare not idempotent conda/conda#870312 remaining items
luabud commentedon Sep 17, 2019
Don Jayamanne (@DonJayamanne) would the proposed solution below work? Do you think this could cause problems for those who are not using conda?
DonJayamanne commentedon Sep 17, 2019
Yes we can do that, however I'm tempted to do the following:
usersettings.jsonChanging settings without users consent is not something we should be doing.
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.
Not that I'm aware of. We can find out.
DonJayamanne commentedon Sep 17, 2019
See PR in progress #6959
luabud commentedon Sep 19, 2019
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 commentedon Oct 8, 2019
Closing in favour of #7607