Closed RMeli closed 5 years ago
Thanks for reporting this issue.
settings.json
and change the value of terminal.integrated.inheritEnv
to false
Closing this issue for the moment. If that doesn't fix it, please let us know and we'll be happy to reopen this issue. Or feel free to create a new issue.
Hi @DonJayamanne, thanks for your reply. I've been following conda
-related issues in VSCode for a while and already tried "terminal.integrated.inheritEnv": false
.
I'm now able to activate a conda
environment before opening any Python file, but as soon as I open a Python file and the Python extension is activated I run into the problem described above.
What version of Conda do you have on your machine?
conda --version
It's conda 4.6.14
on macOS and conda 4.7.5
on Ubuntu 18.04; they both suffer the same problem.
Duplicate of #3834
Environment data
Expected behaviour
I expect the Python extension to activate the correct extension in the integrated terminal.
Actual behaviour
The following error appears on the freshly open terminal:
When I open a new VSCode window and then open a new terminal, the following commands work as expected:
Then, I open a Python file (
.py
) and select the correct Python environment in VSCode (Python 3.6.8 64-bit ('testenv': conda)
). If I now open a new terminal, the following problem occurs:And the
conda
environment is stuck to the one loaded by default in my.zshrc
(and not the one correctly selected via VSCode). Even more concerning, the following (which was working on the first terminal) does not work anymore:i.e. the Python interpreter remains stuck to the default one (Python 3.7).
Steps to reproduce:
conda
environment)Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)