Python venv not recognized when in multi root workspace

[thomasfinstad]

Ha have a multi root workspace where one of the folders (where I am developing the python script) has a .venv folder, recognized by vscode.

When running the quick discover function the venv is not recognized and the extension tries to run homebrew python instead.
This might be because the folder with the venv is not the first one in the list, when I try the "select installer" option it only seems to look in the first folder.

I recreated this by

1. creating a new workspace,
2. adding one folder with no venv
3. adding another folder, and creating a venv in it
4. add another folder with no venv
5. create a python file in the folder with a venv
6. make sure vscode notice the venv and behaves as expected (I just made the venv with a python version that is not my default so it was easy to see that it was active)
7. running auto discover it says my default python needs to install it instead of the venv
8. trying to select installer only shows pip from the first folder in the workspace list

[vemel]

Multi-root workspace is currently not supported. Sorry for the late response.