microsoft / microsoft/vscode-python-environments
The automatic activation mechanism has been damaged
@anthonykim1 is already working on this.
Since Feb 5, 2026.
- Dominant language
- TypeScript
- Stars
- 138
- Forks
- 62
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 35
Description
Before, my terminal in VSCode will keep conda env activated automatically without `conda init`, when I choose a python interpreter.
But now, it break my python env auto activation. When I use code runner to run a python script in a new terminal, the terminal don't activate in the desired python interpreter, but use the default base env of conda. **I want to solve how can I keep workshop's terminal in desired python interpreter env when as soon as I open it without using any commands.**
**My core problem is the terminal don't keep in the workshop's python interpreter env, but when I open terminal, it run `Anaconda/Scripts/activate` to activate env, which report "CondaError: Run 'conda init' before 'conda activate'", but i don't want use `conda init` to pollute my terminal.**
I'm not a professional developer, my description might be somewhat inappropriate. For more information please ask me.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.