microsoft / microsoft/vscode-python-environments

VS Code discovers Conda environments but Python: Select Interpreter does not display them

オープン
#1,671 コメント 8 件 リアクション 0 件 担当者 1 名 GitHub で見る

@StellaHuang95 がすでに取り組んでいます。

2026年8月5日 から。

bug triage-needed
主要言語
TypeScript
スター
138
フォーク
62
平均マージ
1日 4時間
マージ済み PR(30日)
35

説明

Does this issue occur when all extensions are disabled?: N/A, need python extension to get it to work

VS Code discovers Conda environments but Python: Select Interpreter does not display them

Environment

  • VS Code: 1.130.0
  • OS: macOS (Apple Silicon)
  • Conda: 26.3.2
  • Python Environments extension: 1.36.0
  • Python extension: current release at time of filing
  • Pylance: current release at time of filing

Problem

VS Code no longer displays my Conda environments in the interpreter picker.

When I run Python: Select Interpreter, I only see:

  • System Python
  • Any interpreter that was manually selected previously
  • Enter Interpreter Path
  • Create Virtual Environment

My Conda environments are not listed.

However, manually selecting an interpreter by path works correctly.

For example, if I manually select:

<conda-install>/envs/<env-name>/bin/python

the environment works normally afterward.

The issue is specifically that discovered Conda environments are not shown in the interpreter picker.

Steps to Reproduce

  1. Install Miniforge/Conda and create one or more Conda environments.
  2. Verify that the environments exist:
conda env list
  1. Open VS Code.
  2. Install and enable:
    • Python
    • Python Environments
    • Pylance
  3. Open a workspace/folder.
  4. Run:
Python: Select Interpreter

Expected Behavior

All discovered Conda environments should appear in the interpreter picker.

For example:

base
<env-1>
<env-2>
...

Actual Behavior

The interpreter picker only displays:

System Python
Enter Interpreter Path
Create Virtual Environment

along with any interpreters that were manually selected previously.

Discovered Conda environments are not shown.

Evidence From Logs

The Python Environments extension reports that Conda environments are being discovered successfully:

Environment discovery complete: 9 environments found (Global: 1, Conda: 8)

Example log entries:

Using conda from persistent state: <conda-install>/bin/conda

Found named environment: <env-1>
Found named environment: <env-2>
Found named environment: <env-3>

Discovered env:
<conda-install>/envs/<env-1>/bin/python

Discovered env:
<conda-install>/envs/<env-2>/bin/python

Discovered env:
<conda-install>/envs/<env-3>/bin/python

The logs indicate that environment discovery is functioning correctly, but the discovered environments are not displayed in the interpreter picker UI.

Troubleshooting Already Attempted

Verified Conda is functioning correctly:

conda env list

returns all expected environments.

Verified Conda executable is present:

which -a conda
conda info --base

Both return expected results.

Verified the integrated VS Code terminal can use Conda normally.

Verified that manually selecting an interpreter path works and the selected environment functions correctly.

Executed:

Python: Clear Workspace Interpreter Setting

and then:

Developer: Reload Window

Deleted the Python Environments extension cache:

~/Library/Application Support/Code/User/globalStorage/ms-python.vscode-python-envs

Deleted VS Code workspace storage:

~/Library/Application Support/Code/User/workspaceStorage

Restarted VS Code.

Reinstalled VS Code completely.

Issue persists.

Additional Notes

The problem appeared suddenly after previously working correctly.

The integrated terminal is able to use Conda normally, and the Python Environments extension consistently reports successful Conda environment discovery.

This appears to be an issue where discovered Conda environments are not being surfaced in the interpreter picker UI despite being successfully discovered by the Python Environments extension.

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。