Repository navigation
Conda activation does not work in Terminal #5764
Description
Activity
- changed the title
[-]Even though conda env is activated `python` points to default `python` interpreter[/-][+]Conda activation does not work in Terminal[/+]on May 24, 2019 I have exactly the same problem. Conda env activation doesnt't work from vscode, but works fine from iTerm/Terminal.
I seem to be having the same problem (identical to microsoft/vscode#72188)
12 remaining items
Don Jayamanne (@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
Yes we can do that, however I'm tempted to do the following:
- Prompt and change the setting in
usersettings.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.
Reacted by Luciana Abud- Prompt and change the setting in
See PR in progress #6959
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, NoAnd add telemetry for the yes selection, so we can know if this is actually solving the issue.
Reacted by Don JayamanneClosing in favour of #7607
- locked as resolved and limited conversation to collaborators
on Oct 15, 2019
Environment data
Expected behaviour
When a conda environment activated using
conda activate xxx, then usingpython xxxwill point to the activated environment.Actual behaviour
Even though a conda environment has been activated,
which pythonwill point to the wrong environment.Steps to reproduce:
conda activate xxxwhich pythonTracked here #5344
Upstream issue microsoft/vscode#70248