Allow .vscode/settings.json per folder without using multi-root workspaces

[yegorski]

Specifically we're interested in having the python.defaultInterpreterPath setting to be folder-specific. Right now in our Python monorepo, navigating between projects requires manual switching of the Python interpreter so that the pip packages and imports are recognized by the IDE.

I'm imagining the end state where each project in the monorepo has its .vscode/settings.json file and have VS Code read the settings from that file when a file from that project is open.

More context: Multi-root workspaces won't work here. We're using the Pants build tool. While it's a monorepo, it's more than just several top-level folder smooshed together. There are other metadata files at the top-level so we can't really have a project.code-workspace file because we'll need the . folder to be included and that causes the other folders to be duplicated in the explorer view.

Issues I found that are related but not applicable:

1. Add ability to extend from other settings files #15909
2. Add support for additional global config files (in addition to settings.json) #17634
3. Allow several settings.json #147911

[brettcannon]

This sounds more Python-specific than anything, so transferring over there.

[karrtikr]

It would be difficult to solve it from Python extension's perspective as this requires us to look for python.defaultInterpreterPath setting in various settings.json files in the workspace folder. If you would still like us to consider it please open a feature request in https://github.com/microsoft/vscode-python/issues.

I'm transferring it back to VSCode as this requires a general solution like #15909 IMO.

[karrtikr]

We've opened microsoft/vscode-python#21204 in Python extension to track this support.

[sandy081]

/duplicate

#32693

[vscodenpa]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!