Environment Selection bar disappeared in Interactive Window

Bug: Notebook Editor, Interactive Window, Editor cells

Steps to cause the bug to occur

1. Open VS Code
2. Ctrl+Shift+P, Python Interactive Window

Actual behavior

The bar that shows current kernel/environment flashes as interactive window launches, and then completely disappears.

Expected behavior

In the Interactive Window, on top of control buttons, there used to be a bar that shows current kernel/environment, which you can click on and switch if needed.

Your Jupyter and/or Python environment

Please provide as much info as you readily know

• Jupyter server running: Local
• Extension version: 2020.9.111407
• VS Code version: 1.49.2
• Setting python.jediEnabled: true | false
• Setting python.languageServer: Jedi | Microsoft | None
• Python and/or Anaconda version: 3.6.10 64-bit
• OS: Windows 10 1909
• Virtual environment: virtualenv

Python Output

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

[greazer]

Current thoughts:

1. Add a setting to bring back old behavior – not discoverable.
2. Add a command to change kernel for active interactive window – This is our current favorite idea.
3. Just revert back to the old behavior – The reason we made this change was to alleviate user confusion overall, since we had that feedback.

More discussion will happen over the next couple weeks.

[volopasse]

Would like to add another use case, that appears to have been dropped with this change.

I have several kernels using one interpreter. These are in ~/.local/share/jupyter/kernels, and some are manually edited (e.g. to include environmental variables). Previously I was able to select the specific kernel from there, but with this new approach I no longer have that flexibility.

I would also second @elvissey1984 's point about quickly selecting the kernel, and also knowing which one you’re using at the moment. Once again, I’m not sure how many people have different kernels under the same interpreter, but this functionality has been lost