Project Wizard: Python project environment step - Venv

[sharon-wang]

New Project Configuration

Config	Value
Project Type	Python or Jupyter
Step	Set up Python environment
Environment Setup Type	New Environment
Environment Type	Venv

Expected UI/UX

For the Python environment configuration step in the Project Wizard, when creating a new Venv environment:

• There is a note that previews the path of the environment that will be created
• Project Wizard: detect if ipykernel is installed for the selected interpreter #2856
• If suitable python interpreters are detected
  • The preferred python interpreter is selected by default
  • The interpreter options are filtered to Global Python interpreters only
  • The python interpreter can be changed to something else available in the dropdown
• Project Wizard: provide feedback if no supported interpreters detected #3101
• Once the new project is created
  • a venv is created
  • ipykernel is pre-installed
  • the python in the venv is the active interpreter

Related

• Feature Request: Create New Folder w/ venv #1441

[sharon-wang]

Moving out of "Ready for Verification".

The changes from #3305 cause the newly created Venv to start before we've had a chance to install ipykernel, resulting in the ipykernel install dialog popping up.

We'll need a way to tell the extension to not auto-start the newly created Venv for a new project, or otherwise inform the extension that we'd like ipykernel installed by default when we create a new Venv.

Additionally, Venvs are created even when a user opts to use an existing interpreter. That's a bug! 🐛 I've moved #2840 out of verification as well.

[testlabauto]

Verified Fixed

Positron Version(s) : 2024.05.0-1345
OS Version          : OSX

Test scenario(s)

New project creation with venv looks good, including ipykernel install

Link(s) to TestRail test cases run or created: