You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9b6ae37
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+1-7Lines changed: 1 addition & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,13 +65,6 @@ The following environment managers are supported out of the box:
65
65
66
66
Environment managers are responsible for specifying which package manager will be used by default to install and manage Python packages within the environment (`venv` uses `pip` by default). This ensures that packages are managed consistently according to the preferred tools and settings of the chosen environment manager.
67
67
68
-
The built-in `venv` environment manager uses separate standard-library venv and uv creation
69
-
backends. Creation automatically uses uv when the existing uv policy allows it and uv is available
70
-
to the creation scope; otherwise it uses `python -m venv`. Backend execution errors are reported
71
-
without retrying through the other backend. Both kinds of virtual environment retain the same
72
-
`ms-python.python:venv` manager identity, discovery, selection, and removal behavior. Backend
73
-
selection does not hide existing environments when uv availability or `python-envs.alwaysUseUv` changes.
74
-
75
68
### Package Management
76
69
77
70
The extension also provides an interface to install and uninstall Python packages, and provides APIs for extension developers to contribute package managers of their choice.
@@ -95,6 +88,7 @@ manager explicitly always uses uv, independently of that setting. The uv package
95
88
uv from PATH, a current-session installation, or the requesting trusted workspace's `.pyprojectx/main/uv`
96
89
(`uv.exe` on Windows). If uv is unavailable, it reports an error rather than falling back to pip.
97
90
Scoped requests use the project to discover uv even when the target environment is outside the workspace.
91
+
Explicit uv selection also retains this scope for project-tree package operations.
98
92
Package mutations invalidate both built-in backends' cached inventory for the target environment,
99
93
so switching between pip and uv does not reuse a snapshot from before the mutation.
0 commit comments