Breaking: Microsoft Rolls Out Python Environments Extension for VS Code
Microsoft today announced the general availability of the Python Environments extension for Visual Studio Code, ending a year-long preview that saw thousands of developers testing the unified environment manager. The extension replaces fragmented workflows across tools like venv, conda, pyenv, poetry, and pipenv with a single, streamlined interface.
"This extension addresses the number one pain point we heard from Python developers: managing environments shouldn't be a project in itself," said Mark Johnson, Product Manager at Microsoft. "After a year of community feedback, we're confident this delivers a consistent experience."
The rollout will begin automatically for most users over the next few weeks, but developers can opt in immediately by setting python.useEnvsExtension to true in their VS Code settings. The extension requires no additional setup—opening a Python file triggers automatic environment discovery.
Unified Environment Experience
The extension automatically discovers environments from all major managers: venv, conda, pyenv, poetry, pipenv, and system Python installs. Discovery is powered by PET (Python Environment Tool), a Rust-based scanner that checks PATH, known installation locations, and configurable search paths.
"PET has already proven itself in the existing Python extension," Johnson explained. "Now we've built a dedicated UI around it, giving developers one place to create, delete, switch, and manage environments, regardless of which tool created them."
For environments in non-standard locations, users can configure workspace-level search paths with glob patterns or set global search paths for shared directories.
Faster Environment Creation with uv
If the uv tool is installed, the extension uses it automatically for creating venv environments and installing packages, delivering significantly faster performance—especially in large projects. This behavior is enabled by default via the python-envs.alwaysUseUv setting.
Quick Create and Custom Create
The extension introduces two new creation workflows. Quick Create (the '+' button in the Environment Managers view) builds an environment using the default manager, the latest Python version, and workspace dependencies from requirements.txt or pyproject.toml. "It's a working environment in seconds," noted Dr. Sarah Chen, a data scientist and early adopter.
When more control is needed, Custom Create (via Python: Create Environment in the Command Palette) lets users choose their environment manager, Python version, environment name, and which dependency files to install from. Currently, venv and conda support direct creation from VS Code; for pyenv, poetry, and pipenv, the extension discovers environments created via their respective CLI tools.
Python Projects: Environments That Match Your Code Structure
The extension introduces Python Projects, which map environments to specific folders or files—solving common problems in monorepos. This ensures each project component uses the correct interpreter and dependencies without manual switching.
Background
Python developers have long struggled with fragmented environment management. Each tool—venv, conda, pyenv, poetry, pipenv—offered different workflows, making it hard to switch between projects or collaborate across teams. The Python Environments extension began as a preview a year ago, collecting feedback from over 100,000 users. Microsoft refined PET and the UI based on real-world usage, aiming to reduce context switching.
What This Means
For individual developers, the extension eliminates the need to remember multiple CLI commands. For teams, it enforces a consistent environment setup across projects, reducing "it works on my machine" bugs. The integration with uv also promises faster CI/CD pipelines, as environment creation can be accelerated in automated builds.
"This is a game-changer for onboarding new team members," said Alex Rivera, a senior developer at a fintech startup. "Now I can point them to VS Code and they're productive immediately, without needing to learn three different environment tools."
However, the extension does not replace the underlying tools—developers can still use their preferred manager's CLI. The extension simply provides a unified front end, leaving the existing workflows intact. As Johnson summed up: "We're not asking anyone to give up their favorite tool. We're just making it easier to use them all from one place."
The rollout begins immediately. Users on the latest version of VS Code and the Python extension will receive the update automatically within weeks.