microsoft / microsoft/vscode-python-environments
The automatic activation mechanism has been damaged
@anthonykim1 已经在做这个了。
开始于 2026年2月5日。
- 主要语言
- TypeScript
- 星标
- 138
- 派生
- 62
- 平均合并
- 1 天 4 小时
- 30 天内合并 PR
- 35
描述
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.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
评估
这个 Issue 还没有评估数据。