Unable to select interpreter to start Jupyter server

[leonarduschen]

Environment data

• VS Code version: 1.51.1
• Jupyter Extension version (available under the Extensions sidebar): v2020.11.372831992
• Python Extension version (available under the Extensions sidebar): v2020.11.371526539
• OS (Windows | Mac | Linux distro) and version: Windows 10
• Python and/or Anaconda version: 3.8.5 32-bit
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
• Jupyter server running: Local

Expected behaviour

Works just fine

Actual behaviour

Select interpreter does nothing and Jupyter keeps prompting ipykernel to be install to my other interpreter 3.8.3 64-bit (conda) - which is my conda base environment. I have also tried creating new venv and conda environments and got the same results.

Also, it keeps asking for feedback for some reason, perhaps it is related to #4034

Steps to reproduce:

• Open VSCode
• Run python -m venv venv
• Click yes when prompted to select the new virtual environment for the current working directory
• Create new .ipynb file and open it

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

XXX

[claudiaregio]

Hi @leonarduschen, does this happen constantly? Have you tried restarting VS Code? Also, could you provide a gif showing us what you are seeing? If you need a tool ScreenToGif works pretty well (https://www.screentogif.com/)

[leonarduschen]

Have you tried restarting VS Code?

Yes and tried using multiple Python versions in conda environment too - but Jupyter keeps using my base conda interpreter 3.8.3 64-bit (conda) for some reason. Perhaps this is related to #4037.

That said, I ended up deleting Python (e.g. interpreter, conda, etc), installed Python 3.9.0 64-bit and it works fine now. Feel free to close the issue. But it still constantly asks for feedback - same issue as #4034

Also if it helps at all: this issue comes out of nowhere, maybe a recent update causes this?

Update: works fine now for some reason. Feel free to close the issue.

[claudiaregio]

Ok great, thanks for the update!