Python: Iteration Plan for May 2023

[kieferrm]

This plan captures our work in May 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
  • Investigate adding entries in problems window when requirements.txt has missing libraries; issue; @karthiknadig
  • Investigate adding entries in problems window when pyproject.toml has missing libraries; issue; @karthiknadig
• 🏃‍Implement new getting started experience in the walkthrough; issue; @cwebster-99
• 🏃‍🔵 Get better understanding of pain points related to Python mono repo experience; issue; @luabud @cwebster-99

Environments

• Create an npm types package for public extension API; issue @karrtikr

Editing

N/A

LSP

• ⬛ ‍Add Rust support to lsprotocol; issue; @karrtikr @karthiknadig
  • Familiarize with LSP and Rust plugin for lsprotocol; issue; @karrtikr
• 🏃‍♀️ ⬛ ‍Add Dotnet support to lsprotocol; issue; @karthiknadig
• 💪 ⬛ Notebook support for linting and formatting; issue; @karthiknadig
  • 💪 Implement Notebook support in pygls; issue ; @karthiknadig

Terminal

• Incorporate fixes from VS Code regarding Environment collection API; 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
• Update localization 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

Formatting

N/A

Linting

N/A

Testing

• Debugging support for pytest; vscode-python#21147 @eleanorjboyd
• ⬛ 🏃‍ Dynamic run result in test explorer for pytest; vscode-python#21148 @eleanorjboyd
• ⬛ 🏃‍ Dynamic run result in test explorer for unittest; vscode-python#21149 @eleanorjboyd
• Rollout discovery and execution for pytest and unittest; vscode-python#21150 @eleanorjboyd @cwebster-99
• Support multiroot and large scale testing repos in both unittest and pytest vscode-python#21309 and vscode-python21308 @eleanorjboyd

vscode.dev

N/A

Documentation

• 🏃 Freshen up docs; issue; @brettcannon @luabud @dawnwages
• Enhance Python tutorial and environments doc; issue; @cwebster-99

Engineering

• 🏃 Onboard ESRP Release pipelines; issue; @karthiknadig

Python community

• ⬛ 🏃‍ Enriched/strict package.metadata parsing; PR; @brettcannon
• 🏃‍ Write down build process for WASI in https://github.com/python/cpython/blob/main/Tools/wasm/README.md ; @brettcannon
• 🏃‍ Update CPython dev container definition; 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