Python: Iteration Plan for February 2024

[kieferrm]

This plan captures our work on the Python Extension in February 2024. 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

• Design opinionated flow for package installation; issue; @cwebster-99 @karthiknadig

Environments

• Use webworker for Conda & Windows registry when discovering environments; issue; @karrtikr
• ⬛💪🏃‍♀️ Explore supporting version constraints for various tools for automatic environment selection; pyenv; @karrtikr
• ⬛🏃‍♀️ Investigate API for workflow contributions; issue; @karthiknadig
• Environment management user study; issue; @cwebster-99

Editing

N/A

Terminal

• 🏃‍♀️ Address concerns with terminal activation experiment; issue; @karrtikr

REPL

• Use shell integration to support shell file history; issue; @anthonykim1
• 🏃‍♀️ Fix shell integration bugs; issue; issue; @anthonykim1
• Investigate and fix how to lower the risk of losing the first pasted line into the REPL; issue; @anthonykim1
• 🏃‍♀️ Investigate a VS Code-native REPL experience; issue; @anthonykim1

Debugging

• Use the ports API to ignore all ports; issue; @paulacamargo25
• ✋🏃‍♀️ Improve "Run and debug" button support; issue; @paulacamargo25
• Look into test debugging stability/configuration; issue; @paulacamargo25
• Server state ready for auto-launch for Django, Flask, and FastAPI; issue @paulacamargo25
• 🏃‍♀️ Django and Flask startup script selection; issue @paulacamargo25

Formatting

N/A

Linting

N/A

Testing

• Design custom arguments for test discovery and execution; issue; @eleanorjboyd
• 🏃‍♀️ Switch to named pipes for testing communication; issue; @eleanorjboyd @karthiknadig
• 🔵🏃‍♀️ Adopt proposed API for testing coverage feature; issue; @eleanorjboyd
• 🏃‍♀️ Fix remaining issues to remove test rewrite experiment code; issue @eleanorjboyd
• 🏃‍♀️ Plan custom args user study; issue; @eleanorjboyd @cwebster-99

vscode.dev

N/A

Documentation

N/A

API

N/A

Engineering

• 🏃‍♀️ Isolate Python code so it doesn't conflict with user code; issue; @karthiknadig

Python community

• Get WASI to tier 2 support for CPython; issue; @brettcannon
• Add WASI to CPython CI; discussion; @brettcannon
• 🏃‍♀️ PyCascades planning; @dawnwages @luabud

---

Deferred Items

• Investigate contributing a callout for automatic configuration in Debug Start View; issue; @paulacamargo25
• 💪 Start refactoring code for custom args; issue; @eleanorjboyd
• 🏃‍♀️ ⬛ Implement a dependency resolver with a customizable API; @brettcannon
• 🏃 Add launch support for test discovery and execution in settings.json; issue @eleanorjboyd
• 🏃 Adopt the proposed port attributes API in testing rewrite; issue @eleanorjboyd
• 🏃‍♀️ Pre-release of debugger extension using debugpy 1.5.1; issue @paulacamargo25
• ⬛ ‍Add Rust support to lsprotocol; issue; @karrtikr @karthiknadig
• 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
• ✋ Make tests work with symlinks; issue @eleanorjboyd
• 🔴 💪 Investigate a contribution point for workflow extensions; @karthiknadig