Repository navigation
Deleting .venv outside VS Code leaves the deleted interpreter selected #1886
Description
Activity
Sharing media and context from merged PR #1889 for verification:
Deleting a virtual environment folder outside VS Code (for example
rm -rf .venv) now refreshes the venv manager, so the deleted interpreter is no longer selected. Previously the status bar kept showing it until reload.registerSystemPythonFeatures: a second watcher listens for deletions only (**/*). VS Code reports a deleted folder as the folder alone, so the existing**/activatewatcher never fires for it.VenvManager.hasEnvironmentAt: the delete handler triggers the existing debounced refresh only when the deleted path is, or contains, a known venv; other deletions are ignored. The check is one set lookup (about 2.6 µs per deletion whatever the number of venvs), so bulk deletions such as clearing__pycache__stay cheap.- Not changed: venvs outside the workspace folders are not watched, as before.
Before / after
Folder with
.venv(Python 3.13.15);.venvdeleted from outside VS Code.Before
After
Validation
Check Result UI scenario on main@ 52f6ace❌ status bar still shows the deleted .venvafter 30 sUI scenario with this PR ✅ switches to Python 3.14.8 in ~3 s, 3/3 npm run lint,npm run compile-tests,npm run unittest✅ 2545 passing (new tests in main.unit.test.ts)
Created by Copilot
Source PR: #1889
- added a commit that references this issue
on Oct 6, 2026
Problem: Deleting a workspace virtual environment outside VS Code (for example
rm -rf .venvin a terminal) leaves it selected. The status bar keeps showing the deleted.venv, and Run, terminals and Pylance keep pointing at an interpreter that no longer exists until the window is reloaded or environments are refreshed manually.The venv manager refreshes on changes to
**/activatefiles. VS Code reports a deleted folder only as the folder itself (events for the files in it are dropped), so deleting the whole venv folder never matches.Environment: Windows 11, VS Code 1.140.0, extension
main@ 52f6ace.Before:
Steps to verify fix:
.venvand open a.pyfile; verify the status bar shows.venv.rm -rf .venvorrmdir /s /q .venv).python -m venv .venv) and verify the status bar switches back to.venv.Found by Copilot