Repository navigation
Python: User Interpreters Frozen #25652
Description
Activity
- addedtriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
on Dec 11, 2025 - assigned and unassigned
on Dec 11, 2025 - removedtriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
on Dec 11, 2025 - addedtriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
on Dec 12, 2025 is this new to this release? If you go to the previous release does that fix it or has this been happening for a few releases
- addedinfo-neededIssue requires more information from posterIssue requires more information from poster
on Dec 12, 2025 flaviosantoshidromod commented
on Dec 12, 2025 AuthorMore actionsOn the previous release this was not an issue. I have noticed though that switching back the Python Environments extension to the Pre-Release version, this issue is resolved.
So far that's how I'm working. It does however signal an incompatibility between the new VS Code and the latest Python Environments release
- removedinfo-neededIssue requires more information from posterIssue requires more information from poster
on Dec 12, 2025 - addedregressionBug didn't exist in a previous releaseBug didn't exist in a previous releaseconfirmation pendingThe issue needs to be confirmed through a maintainer reproducing the bug.The issue needs to be confirmed through a maintainer reproducing the bug.bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug
on Dec 16, 2025 - removedtriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
on Mar 13, 2026 🤖 Thanks for the follow-up. Since switching only the Python Environments extension to its pre-release build resolved this, could you confirm whether the problem still occurs with the latest Python and Python Environments extensions? A closely matching Windows/conda discovery failure was fixed by microsoft/vscode-python-environments#1102 and shipped in Python Environments v1.18.1. If it still reproduces, please include the Python Environments output so a maintainer can transfer this to https://github.com/microsoft/vscode-python-environments with the needed diagnostics. Issues marked info-needed automatically close after 30 days without a reply.
- addedinfo-neededIssue requires more information from posterIssue requires more information from poster
on Sep 23, 2026
Does this issue occur when all extensions are disabled?: No
VS Code Version: 1.107.0 (user setup)
Commit: 618725e67565b290ba4da6fe2d29f8fa1d4e3622
Date: 2025-12-10T07:43:47.883Z
Electron: 39.2.3
ElectronBuildId: 12895514
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26100
My created conda python environments are not available for selection in the Python: Select Interpreter option for new workspaces. Older workspaces work fine, with the previously attributed environments. Manually finding the environment is also broken as nothing happens when I navigate manually to previously created conda environments
New (created just now) workspace:
Older workspaces: