venv not detected when created with Anaconda base environment

Environment data

• VS Code version: 1.36.1
• Extension version: 2019.8.29288
• OS and version: Windows 10 1803 b17134.885
• Python version: Python 3.7.4, Anaconda 4.7.11
• Type of virtual environment used: venv, conda
• Relevant/affected Python packages and their versions: N/A
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): false

Expected behaviour

No matter which anaconda environment is active after running python -m venv venv, the extension will detect the new python environment in the folder venv.

Actual behaviour

The extension does not detect venvs created from the base environment, but will if created from another environment.

Steps to reproduce:

1. Install anaconda, then run conda init from the anaconda PowerShell prompt and restart. This adds the following to your profile:

(& "C:\Users\GGallo\AppData\Local\Continuum\anaconda3\Scripts\conda.exe" "shell.powershell" "hook") | Out-String | Invoke-Expression

1. In VS Code, create a clean directory and cd inside. Make this the base of a new workspace. The rest happens on an integrated terminal.
2. conda activate to make sure you have the base environment.
3. python -m venv venv. Check for new interpreters, the new venv does not appear.
4. rm -Recurse -Force .\venv
5. conda create --name test python
6. conda activate test
7. python -m venv venv. Check for new interpreters, there it is!

Sorry I can’t GIF this whole thing, not an option right now.

You can even conda remove --name test --all and the venv will continue operating as normal.

[brettcannon]

@ggallo it is an atypical setup because you need to have the conda environment activated in order for things to work appropriately.

But in your screenshot you have source/ open, but your virtual environment is in source/clean/venv. We only automatically detect at the top of your open folder, so we would never notice that virtual environment. I would either create directly under source/ or set "python.venvPath" to point to clean to notice that venv/ folder.

[DonJayamanne]

Thanks for figuring that out @brettcannon