Detect virutal envs recursively in all sub-directories in the workspace

This issue is similar to #2470 but the solution doesn’t apply to me. I tried changing the “python.venvPath”: “${workspaceFolder}/venv” in setting.json but it didn’t help. As it can be seen in the screenshot, I can use the virtual environment using terminal.

Environment data

• VS Code version: 1.45.1
• Extension version (available under the Extensions sidebar): 2020.5.80290
• OS and version: ubuntu 18.04 (Linux x64 4.15.0-101-generic)
• Python version (& distribution if applicable, e.g. Anaconda): python 3.6.9
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): venv
• Relevant/affected Python packages and their versions: XXX
• Relevant/affected Python-related VS Code extensions and their versions: XXX
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): true
• Value of the python.languageServer setting: “Microsoft”

Expected behaviour

Clicking on the interpretor on the left bottom should show all available interpretors including virtual environments.

Actual behaviour

virtual environment are not detected.

Steps to reproduce:

1. click on the interpretor selection on the left bottom

Logs

[karthiknadig]

@PooyaJln With python.venvPath we only look in the immediate sub-directories. So if the venv folder is two levels down we will not automatically detect it. This would be an enhancement to how we detect virtual envs in the workspace.

[luabud]

Thanks for bringing this up, folks! I opened https://github.com/microsoft/vscode-docs/issues/3789 so we can update our docs to reflect that 😊

@yuvadm our plan is to deprecate the pythonPath setting, so you’ll still be able to select interpreters per workspace but that info won’t be stored in the settings.json file. We have this change on as an experiment, you can learn more about it here: https://github.com/microsoft/vscode-python/wiki/AB-Experiments#experiment---deprecatepythonpath