pythonProjects setting messed up with remote multi-root environment #1094
Description
I have a multi-root workspace, working inside a devcontainer (inside WSL). My workspace file has this:
"folders": [
{
"path": ".."
},
{
"path": "../external/Y"
}
]
In my devcontainer settings (so VS Code remote settings), I have the pythonProjects defined:
"python-envs.pythonProjects": [
{
"path": "systemtests",
"envManager": "ms-python.python:venv",
"packageManager": "ms-python.python:pip",
"workspace": "X"
}
]
The X workspace is the name of my first folder. On that folder, I also have settings, where there is also pythonProjects:
"python-envs.pythonProjects": [
{
"path": "systemtests",
"envManager": "ms-python.python:venv",
"packageManager": "ms-python.python:pip"
}
]
Whenever my window is reloaded, when I click on the Python icon on the side bar, the extension writes into my workspace file, adding a pythonProjects setting with:
"python-envs.pythonProjects": [
{
"path": "systemtests",
"envManager": "ms-python.python:venv",
"packageManager": "ms-python.python:pip"
}
]
Two problems here:
- why is it adding that setting to my workspace file? It works perfectly fine without it; I can delete it, the extension reloads settings, and everything works.
- that workspace setting is wrong, since it doesn't have the workspace it belongs to! So, on a multi-root workspace as I have, that systemtests path is being applied to both folders and showing up both on the Python Projects list (although the second folder doesn't have such a systemtests folder!).
Let me know if you need more information or logs.