Repository navigation
Stale interpreter label for virtualenv showing old Python version despite executable being Python 3.14 #25691
Closed as not planned
Description
Summary
The VS Code Python extension shows a stale interpreter label (e.g., "venv (3.13.4)") for a workspace virtual environment even though the virtual environment's python.exe is Python 3.14.0 and pyvenv.cfg shows version = 3.14.0.
Environment
- VS Code: 1.107.1 (Windows)
- Python extension: v2025.20.1
- Pylance: v2025.10.4
- Project: MeemSaaS (Django)
- Workspace path:
D:\VScode Projects\MeemSaaS - Virtualenv path showing stale label:
D:\VScode Projects\MeemSaaS\backend\venv\Scripts\python.exe(UI label:venv (3.13.4)) - Actual python:
D:\VScode Projects\MeemSaaS\backend\venv_314\Scripts\python.exe->Python 3.14.0
Reproduction steps
- Create a new virtual environment using Python 3.14 and install dependencies (or replace python.exe in an existing venv).
- Open the workspace in VS Code and set the workspace interpreter to the venv path (workspace settings or via interpreter selector).
- Reload the window / restart VS Code.
- Observe interpreter selector: the listed label for the selected path still shows the old Python minor version (e.g., 3.13.4) even though
python --versionin that path reports 3.14.0.
Expected behavior
- The interpreter selector should display the correct Python version that matches the interpreter executable (3.14.0).
Actual behavior
- The interpreter selector displays a stale label (e.g., "venv (3.13.4)").
Additional diagnostic info
- I cleared Python extension caches, fully reinstalled the Python extension and Pylance, and removed temporary metadata caches. The problem persists.
pyvenv.cfgshowsversion = 3.14.0for the new venv.- Tests run via VS Code test runner still pick up the workspace interpreter path internally (the executable is correct), but UI labeling is inconsistent and confusing for users.
Logs / Artifacts
- I can provide VS Code logs (shared process logs, extension host logs), the
pyvenv.cfgfiles, and a screenshot showing the stale label if helpful.
Notes / Possible causes
- This may be caused by caching interpreter metadata (stored label/metadata not invalidated when venv is updated in-place or when Python minor version changes without changing venv path).
Please let me know what additional logs or steps you'd like me to collect. Thanks!
Activity
eleanorjboyd commentedon Jan 5, 2026
Could you please run the Python Environment Tool and share the output? Here’s how:
This will show us which environments VS Code detected and how they were resolved, which is very helpful for debugging interpreter issues 👍
benoitperrin commentedon Jan 13, 2026
Ma'moun Al-zyoud (@mamounalzyoud) I ran into the same issue.
It was "fixed" it by running the command: "Python: Clear Cache and Reload", as suggested here.
VS Code:
Version: 1.107.1
Commit: 994fd12f8d3a5aa16f17d42c041e5809167e845a
Architecture: x64
Operating System:
OS: Linux (Ubuntu 24.04)
Kernel: 6.14.0-37-generic
Architecture: x86_64
Jahongir-Qurbonov commentedon Jan 16, 2026
Same issue Eleanor Boyd (@eleanorjboyd)
I run this in VS Code:
Python: Run Python Environment Tool (PET) in Terminal...github-actions commentedon Feb 15, 2026
Hey Eleanor Boyd (@eleanorjboyd), this issue might need further attention.
Ma'moun Al-zyoud (@mamounalzyoud), you can help us out by closing this issue if the problem no longer exists, or adding more information.
eleanorjboyd commentedon Feb 17, 2026
Hi- sorry about the delay here. Are you still seeing the problem? We did a release 1.20.0 for the python environments extension which has a lot of updates in this area of env selection and storing
github-actions commentedon Apr 13, 2026
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Happy Coding!