Replies: 1 comment
-
As the pop-up window says, it's activated but your shell prompt didn't update. This usually happens if you activate a conda environment as part of your terminal startup (it's basically overwriting what we are doing). You can turn that off in your shell or opt out of activation entirely. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have multiple Python environments on my MacOS computer, including the built-in, brew, and conda.
I'd like the Terminal to automatically activate the environment I've selected whenever I open a new Terminal.
This functionality was working perfectly before the introduction of the new feature (#11039), even though it would always display

conda activate base
.For example, I select "test" env:
But now it use built-in Python:

environment contributions
extension log
vsode setting
conda setting
I have temporarily add
pythonTerminalEnvVarActivation
topython.experiments.optOutFrom
in settings to make it work properly. I'm curious if there's a more optimal solution to resolve this issue. Any suggestions?Beta Was this translation helpful? Give feedback.
All reactions