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
creating a new workspace,
adding one folder with no venv
adding another folder, and creating a venv in it
add another folder with no venv
create a python file in the folder with a venv
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)
running auto discover it says my default python needs to install it instead of the venv
trying to select installer only shows pip from the first folder in the workspace list
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