Python: Iteration Plan for April 2023

[kieferrm]

This plan captures our work in April 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

• ⬛ Implement implicit triggers for the Create Environment command; issue; @karthiknadig
• Use microvenv and pip.pyz for Debian users; issue; @karthiknadig
• 🏃‍ Implement new getting started experience in the walkthrough; issue; @cwebster-99
• Localize the walkthrough; issue; @karthiknadig @cwebster-99

Environments

• Leverage quick pick hover support to explain conda environment lacking a Python interpreter; issue @karrtikr
• Create an npm types package for public extension API; issue @karrtikr

Editing

• Use submenus for related Run menus; issue; @karthiknadig

LSP

• 🏃‍♀️ ⬛ ‍Add Rust support to lsprotocol; issue; @karthiknadig
• Add replayability tests to lsprotocol; issue; @karthiknadig

Terminal

• ✋ Incorporate fixes from VS Code regarding Environment collection API (blocked on VS Code); issue; @karrtikr
• Rollout terminal auto-activation on Insiders; issue; @cwebster-99 @karrtikr

Debugging

• 🏃‍♀️ Hacky prototype VSIX of a debugpy extension; issue; @paulacamargo25
• 🏃 ‍Setup telemetry in the debugy extension; issue; @paulacamargo25
• Create a new extension for debugpy on the Marketplace; issue; @paulacamargo25
• 💪 🔴 Create platform-specific VSIXs for debugpy; vscode-python#17439 @paulacamargo25
• Fix debugging when using internalConsole; issue @karrtikr

Formatting

• 🏃‍ Roll out notification for formatting extensions; @luabud

Linting

• Release mypy extension; issue; @karthiknadig

Testing

• Finalize Pytest Discovery Logic issue; @eleanorjboyd @karthiknadig
• Clean debt like tests, UUID checking, server comms issue and issue; @eleanorjboyd @karthiknadig
• Create dummy test run suites; issue; @eleanorjboyd @karthiknadig
• Write test handler for pytest and unittest run; issue and 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; issue; @luabud
• Create Environment proposed API; issue; @karthiknadig
• Switch to logging support for VS Code; issue; @karthiknadig

Python community

• ⬛ 🏃‍ PyCon US WebAssembly summit planning @brettcannon
• Slides for Python language summit talk; @brettcannon
• Slides for PyCon US talk; @brettcannon
• Dev container for python/cpython; @brettcannon
• ⬛ 🏃‍ Enriched/strict package.metadata parsing; PR; @brettcannon

---

Deferred Items

• ✋ 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
• Investigate how we configure running and debugging
• ✋ Write web tests; issue; @karthiknadig
• Unify venvPath and venvFolders; issue
• 🏃‍ Write Pytest logic for Run Test; issue; @eleanorjboyd @karthiknadig
• 🏃‍ Write testing for pytest discovery; issues; @eleanorjboyd @karthiknadig