Test Python Env Creation/Deletion in Kernel Picker

[DonJayamanne]

Refs: microsoft/vscode-jupyter#11904

• Windows @amunger
• anyOS @roblourens

Complexity: 4

Authors: @DonJayamanne , @rebornix

Create Issue

---

We have improved the new MRU kernel picker and enabled that for all Insider users. Please test following scenarios for the platforms you are assigned to.

Initial setup

• Please install the latest pre-release version of Jupyter and Python extensions
• Install Pyolite extension
• Optionally install Polyglot Notebook extension
• Ensure you have Conda or Python installed

Test creation of Virtual Envs or Conda Env

• Create a new Notebook
• Run a cell
• When prompted to select a kernel create a Virtual Env (or Conda Env) from the kernel picker
• Verify the cell runs to completion after all of the dependencies have been installed
  I.e. ensure you do not have to click Run button again,.

Test deletion of Virtual Envs

• Delete the previous .venv or .conda environment from the terminal
• Go into the kernel picker and click on the refresh button in Python Environments kernel source
• Verify the .venv or .conda environment is removed from the list
  Ensure you do not need to re-load VS Code

[amunger]

I'm not seeing the Pyolite extension, is that in preview somewhere?

[roblourens]

It's called vscode-pyodide

[amunger]

edit - never mind, somehow I got switched back to release Juypyter. Does not repro on pre-release

@DonJayamanne - With vscode-pyodide installed, I don't get prompted to select a kernel when running a new notebook. Pyolite is auto-selected, so I have to disable that extension to hit the test steps correctly

[DonJayamanne]

I don't get prompted to select a kernel when running a new notebook. Pyolite is auto-selected, so I have to disable that extension to hit the test steps correctly

@amunger Please could you file a bug in VS Code for this and assign to @rebornix the related bug is #171385

[roblourens]

This was out in the last release right? What changed since then? Or am I remembering wrong?

[roblourens]

I did some copyediting on the wiki that is linked to from the kernel picker (I like those links, hadn't seen it yet) https://github.com/microsoft/vscode-jupyter/wiki/Jupyter-Kernels-and-the-Jupyter-Extension/_compare/da77b90724cf4d99f534d6a36a1155b2e0128370...477d4ecbed1f8cad3fed9a7b6544b1ecc3ea269c please review

[DonJayamanne]

This was out in the last release right? What changed since then? Or am I remembering wrong?

Are you referring to the WIKI or kernel picker env creation/deletion?

[roblourens]

The kernel picker env creation

[DonJayamanne]

The kernel picker env creation

Minor changes to detection of delted envs.
Basically Python extension doesn't detect deletion of envs well enough.

I've reviewed the changes to the WIKI and looks good, please could you sugegst the same changes here as well https://github.com/microsoft/vscode-docs/pull/5962/files as that's where I got that content (i.e. it will go into the vscode docs)

[eleanorjboyd]

working on this TPI and ran into this bug. Adding it here since it seems more related to python create environment and the kernel picker.

[roblourens]

Will the kernel picker point to the docs page instead of the wiki? Are we duplicating the content?

[roblourens]

Would you expect it to detect right away when the environment is deleted and clear the selected kernel? Is it worth opening an issue for that? If I delete the .venv and run a cell I get this

[DonJayamanne]

Will the kernel picker point to the docs page instead of the wiki? Are we duplicating the content?

Yes, once we ship the relase and docs have been published.

[DonJayamanne]

Is it worth opening an issue for that? If I delete the .venv and run a cell I get this

I'll create an issue for that, we should probably just refresh the list of interpreters at that moment.