Python Environments for VS Code: April 2026 Update – Key Improvements in Q&A

This April, the Python Environments extension for VS Code gets a major refresh. Here’s what changed and how it makes your coding life easier.

What are the key startup improvements in the April 2026 update?

The update brings three major changes to startup performance, especially noticeable in remote and containerized workspaces. First, lazy manager discovery defers detection of Pipenv, pyenv, and Poetry environments until you actually interact with them—like opening a Pipfile or pyproject.toml with a poetry backend. This eliminates unnecessary scanning for the majority of users who rely on venv, uv, or conda. Second, faster environment resolution shortens the path from extension activation to interpreter readiness, reducing overhead during startup and interpreter selection. Third, the default workspace scanning pattern has been narrowed from ./**/.venv to .venv and */.venv, avoiding deep recursive scans that could hang the PET process for 30+ seconds on large projects, especially over Remote-SSH. If you have virtual environments nested more than one level deep, you can add custom paths via the python-envs.workspaceSearchPaths setting.

How does lazy manager discovery work and why is it beneficial?

Lazy manager discovery means that the extension no longer eagerly checks for Pipenv, pyenv, and Poetry environments when it starts. Instead, detection is triggered only when you perform an action that requires those managers—such as opening a project that uses a Pipfile or a pyproject.toml with a poetry backend. This change benefits most users because the vast majority rely on simpler environment managers like venv, uv, or conda, which are already handled efficiently. By deferring the heavy lifting, the extension avoids wasted CPU cycles and I/O, resulting in snappier activation times, particularly in large workspaces or on slower remote connections. You can learn more about the default scanning pattern that complements this improvement.

Why was the default workspace scanning pattern changed?

The previous default pattern ./**/.venv performed a recursive scan of the entire workspace tree for virtual environment folders. On large projects—and especially when working over Remote-SSH—this could cause the Python Environment Tools (PET) process to hang for 30+ seconds during configuration, leading to cascading timeouts and restart loops. The new default, .venv and */.venv, covers the standard layout without deep traversal, significantly reducing startup lag. If your project uses a custom structure with virtual environments nested more than one level deep, you can still include them by adding paths in the python-envs.workspaceSearchPaths setting. This change, combined with lazy manager discovery, makes the extension feel much more responsive out of the box.

What reliability fixes were made to the PET process?

The update introduces two important reliability improvements. First, PET crash recovery ensures that if the PET process crashes mid-refresh, the extension no longer ends up in a broken state with no environments visible. Instead, it retries the refresh after the crash and defensively handles empty or malformed responses, so a transient failure doesn't leave you with a blank environment list. Second, a fix addresses the conda base environment problem: after a window reload, the conda base environment could be incorrectly restored as a different named environment, making it appear that your interpreter selection silently changed. This has now been corrected, ensuring the interpreter selection stays consistent across restarts. These changes make the extension more robust, especially in complex setups.

How does the extension handle package list updates now?

You no longer need to manually refresh the package view after running pip install or pip uninstall. The extension now watches for metadata changes in the site-packages directory and automatically updates the package list. This is a quality-of-life improvement that saves you from repeatedly clicking the refresh button. The auto-refresh works by monitoring file system events, so it reacts quickly to modifications. This feature complements the startup performance improvements by making package management seamless in your workflow.

What happens when creating a terminal in a multi-project workspace?

In workspaces containing multiple Python projects, the extension now prompts you to choose which project’s environment to activate when you create a new terminal. Previously, the extension silently picked one environment, which could lead to confusion or activation of the wrong virtual environment. Now you see a clear selection dialog, ensuring the terminal is set up for the project you intend to work on. This improvement reduces errors and saves time, especially when switching between projects frequently. It’s part of a broader effort to make terminal and environment management more transparent and user-friendly.

How was PowerShell activation on Windows improved?

Virtual environment activation via PowerShell on Windows could fail if the system’s execution policy blocked script execution. The extension now sets a process-scoped execution policy before running the activation script, bypassing any restrictive system-wide policies. This means that running .venv\Scripts\Activate.ps1 or similar scripts will succeed even on locked-down machines, as long as the user has permission to set a policy for the current process. The change is transparent—you don’t need to modify any settings—and ensures that environment activation works reliably for all PowerShell users. This fix is particularly valuable in enterprise environments where execution policies are commonly restricted.