Welcome to this Q&A guide covering the latest update to the Python Environments extension for Visual Studio Code, released in April 2026. This release focuses on faster startup, improved reliability, and better terminal and package management experiences. Below we answer key questions about what changed and how it affects your workflow.
1. How has startup performance been improved in this update?
The extension now activates significantly faster, especially on remote or containerized workspaces. Three key changes were made: First, lazy manager discovery means that environment managers like Pipenv, pyenv, and poetry are only detected when you actually interact with them—for example, opening a project that uses a Pipfile or pyproject.toml with a poetry backend. This avoids unnecessary work for most users who rely on venv, uv, or conda. Second, the path from extension activation to interpreter readiness has been shortened, reducing overhead during startup and interpreter selection. Third, the default workspace scanning pattern was narrowed from ./**/.venv (which recursively scanned the entire workspace) to .venv and */.venv—covering standard layouts without deep traversal. This prevents the PET process from hanging on large projects or over Remote-SSH. If you have nested environments, you can add custom paths via the python-envs.workspaceSearchPaths setting.
2. What reliability improvements were made for the PET process?
Two important fixes enhance reliability. First, if the PET process crashes mid-refresh, the extension now automatically retries the refresh and handles empty or malformed responses defensively. Previously, a transient PET failure could leave you with a blank environment list and a broken state. Second, a fix was applied to the Conda base environment: after a window reload, the base environment could incorrectly be restored as a different named environment, making your interpreter selection appear to have changed silently. This has now been corrected, ensuring that your selected interpreter remains consistent after reloads.
3. How does the update improve package list management?
The extension now automatically refreshes the package list after you run pip install or pip uninstall. Previously, you had to manually refresh the package view to see changes. The extension watches for metadata changes in the site-packages directory and updates the display automatically. This quality-of-life improvement saves time and keeps your environment view accurate without extra clicks.
4. What changes were made to terminal creation for multiple projects?
In workspaces that contain multiple Python projects, creating a new terminal now prompts you to choose which project's environment to activate instead of automatically picking one silently. This gives you full control over which environment is active when you start working in the terminal, preventing accidental activation of the wrong environment and making it easier to manage separate dependencies for each project.
5. How does the extension handle PowerShell activation on Windows now?
Virtual environment activation via PowerShell could fail on Windows if the system execution policy blocked script execution. To fix this, the extension now sets a process-scoped execution policy before running the activation script. This allows .ps1 activation scripts to run successfully even when the global execution policy is restrictive, ensuring reliable environment activation for all Windows users.
6. Were there any other notable fixes or enhancements?
Yes, the update also includes several under-the-hood improvements. For instance, the extension now uses a more robust method to track environment manager configurations, reducing edge cases where environments would not appear. Additionally, performance optimizations were applied to the environment listing when many virtual environments exist, and the extension's integration with the Python extension (Pylance) was made more efficient to avoid redundant queries. These changes collectively make the overall experience smoother and more responsive.