Interpreter display in footer shows python version not virtual environment name

[gmeans]

After the most recent VS Code update I noticed a change in behavior regarding the interpreter display in the footer. When I select a virtual environment, I no longer see the environment name. Just the python version.

This may be Poetry specific as I notice regular venv's show up, however this did work before the update.

Environment data

• VS Code version: 1.49.0
• Extension version (available under the Extensions sidebar): v2020.8.108011
• OS and version: MacOS 10.15.6
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.8.0 64-bit
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): poetry
• Relevant/affected Python packages and their versions: N/A
• Relevant/affected Python-related VS Code extensions and their versions: N/A
• Value of the python.languageServer setting: Pylance (2020.9.4)

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]

Expected behaviour

• The footer used to (unless I'm mistaken) show the virtual environment name of the selected interpreter.

Actual behaviour

• Only the python version is displayed. Python 3.8.0 64-bit

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

With poetry installed, and the venv folder added to settings.

1. Create a project poetry init
2. Install deps so virtual environment is created poetry install
3. Select the interpreter from the dropdown (sometimes you have to reload the window or restart code for it to be picked up).

The footer will say the python version of the virtual environment but not the name.

[kimadeline]

Hi @gmeans, thank you for reaching out!

I've noticed it happening before as well, it depends on which interpreter discovery code returns first. We're planning to address that as part of #12020, so I will be closing this issue and folding it into #12020.

Thanks!