I have a multi-root workspace in VS Code. With "mise.configureExtensionsAutomatically": true, then "python.defaultInterpreterPath": "${workspaceFolder}/.venv" is added to my workspace settings file.
This doesn't work because I have projects set up in my workspace that do not use Python, or even mise. So this causes the Python extension to report errors that it can't find .venv in each of the other projects.
I believe the way to resolve this would be to add the python.defaultInterpreterPath setting to ./projects/project/.vscode/settings.json, not ./projects.code-workspace, so to speak.
I tried the "Mise: Select Workspace Folder" command but I'm not entirely sure it worked, since my settings files were not updated. Perhaps that's the real issue here.
I have a multi-root workspace in VS Code. With
"mise.configureExtensionsAutomatically": true, then"python.defaultInterpreterPath": "${workspaceFolder}/.venv"is added to my workspace settings file.This doesn't work because I have projects set up in my workspace that do not use Python, or even mise. So this causes the Python extension to report errors that it can't find
.venvin each of the other projects.I believe the way to resolve this would be to add the
python.defaultInterpreterPathsetting to./projects/project/.vscode/settings.json, not./projects.code-workspace, so to speak.I tried the "Mise: Select Workspace Folder" command but I'm not entirely sure it worked, since my settings files were not updated. Perhaps that's the real issue here.