Python: Iteration Plan for February 2023

[kieferrm]

This plan captures our work in February 2023. We follow the same iteration cycle as VS Code. Although we plan for a whole iteration, we may not only ship at the end of an iteration but throughout.

Legend of annotations

Mark	Description
🏃‍♀️	work in progress
✋	blocked task
💪	stretch goal for this iteration
🔴	missing issue reference
🔵	more investigation required to remove uncertainty
⚫	under discussion within the team
⬛	a large work item, larger than one iteration

Getting started

• Investigate where to have implicit triggers for the Create Environment command; issue @cwebster-99
• 🏃‍♀️ Clean up settings in various repo templates; issue; @brettcannon

Environments

• ✋ Stabilize extension API issue (blocked on Jupyter giving us the green flag) @karrtikr
• Add a 🔙 button to the environment quickpick; issue; @karthiknadig
• Private API for Jupyter to install a Python interpreter into an empty conda environment; issue; @karrtikr @DonJayamanne

Editing

N/A

LSP

• Jupyter: Mapping between notebook and python ; issue ; jupyter ; @karthiknadig
• Jupyter: De-deduplication of completions in notebooks ; issue; jupyter ; @karthiknadig
• 💪 Python: Client options and telemetry client-side middleware ; issue; @karthiknadig
• 🏃‍ Add telemetry for LSP start failure; issue; @karthiknadig
• ⬛ 🏃‍ Add Rust support to lsprotocol; issue; @karthiknadig

Terminal

• 🏃‍♀️ Extract environment variables from an "activated" conda environment via conda run; issue; @karrtikr
• 🏃‍♀️ Prototype activated terminal for conda using environment context API; issue @karrtikr

Debugging

• 🏃‍ Isolate debugger code in core extension so it can be extracted easily; issue @paulacamargo25
• Hacky prototype VSIX of a debugpy extension; issue; @paulacamargo25

Formatting

• 💪 Rollout of notifying about migrating to the formatting extensions; issue; @
  @karthiknadig
• Stop shipping the isort with the extension; issue; @karthiknadig

Linting

• 🏃‍♀️ Rollout for Pylint and flake8 extension suggestion notifications; @luabud

Testing

• Review and Commit Pytest Plugin (without enabling) issue; @eleanorjboyd @karthiknadig
• 🏃‍♀️ Finalize Pytest Discovery Logic issue; @eleanorjboyd @karthiknadig
• Create Pytest plugin call for Run Test; issue; @eleanorjboyd @karthiknadig
• 🏃‍ Write Pytest logic for Run Test; issue; @eleanorjboyd @karthiknadig

vscode.dev

N/A

Documentation

• 🏃‍ Freshen up docs; issue; @brettcannon @luabud

Engineering

• Direct people to the Jupyter extension when using runFileInteractive; issue; @karrtikr
• ✋🏃‍ Drop Jupyter dependency (blocked on Jupyter/core for better extension recommendation); issue; @luabud
• Call the right API to determine if someone is in treatment/control; issue; @karrtikr

Python community

• 🏃‍ PyCon US WebAssembly summit planning @brettcannon
• 💪 🏃‍ Enriched/strict package.metadata parsing; issue; @brettcannon
• 💪 PyCascades talk slides @brettcannon

---

Deferred Items

• Clean up various repos that set up the Python extension; issue
• Use submenus for related Run menus; issue
• Select an environment based on VIRTUAL_ENV; issue
• ✋ Create platform-specific VSIXs for debugpy (blocked on standardizing on extension pipelines supporting platform-specific VSIXs); vscode-python#17439 @paulacamargo25
• ✋ Finalize Python Launcher plug-in design (blocked on conda's feedback); discussion; @brettcannon
• Support .python-version for pyenv; issue; @karrtikr
• Implement a Python traceback problem matcher in core
• ✋ 🔴 Use conda run when debugging (waiting on the conda team to give us the go-ahead to rely on conda run so fundamentally); @paulacamargo25
• Provide settings to control what environment details are displayed; @karrtikr
• Investigate how we configure running and debugging
• ✋ Write web tests; issue; @karthiknadig
• Create a mypy extension
• Unify venvPath and venvFolders; issue