microsoft / microsoft/vscode-python-environments

The automatic activation mechanism has been damaged

未关闭
#664 35 条评论 0 个 reaction 已指派 2 人 在 GitHub 查看

@anthonykim1 已经在做这个了。

开始于 2026年2月5日。

area-activation bug important needs spike
主要语言
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.

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。