GOVERNANCE.md Editor and Tasks Is Silent on the Python Environments Extension Writing .vscode/settings.json #3757

The shape

GOVERNANCE.md "Editor and Tasks" says every VS Code setting lives in the .code-workspace file and .vscode/ holds only tasks.json and launch.json. The Python Environments extension (ms-python.vscode-python-envs, version 1.40.0) breaks that in any repository that opens a Python file. Its setAllManagerSettings writes the environment-manager and package-manager pair to .vscode/settings.json, at the WorkspaceFolder configuration target. It does so whether the folder or the .code-workspace is open.

Why declaring it in the workspace does not help

With a python-envs.pythonProjects value present in the .code-workspace, setAllManagerSettings still writes the folder file. Its other write paths edit the tracked .code-workspace, which can reload the window and drop an agent session.

Constructed example

$ git status --short
?? .vscode/settings.json
$ cat .vscode/settings.json
{ "python-envs.defaultEnvManager": "example-manager", "python-envs.defaultPackageManager": "example-pkg" }

Proposed text

Add to "Editor and Tasks": a repository shipping Python lists .vscode/settings.json in .gitignore, so the extension's write never reaches a commit. The rule that settings live only in the .code-workspace file stays, and the ignore entry keeps the generated file out of the tree.

Evidence

A downstream Python repository adopted the gitignore entry as its fix, a maintainer decision recorded on its tracker.