Python: Iteration Plan for March 2025

[kieferrm]

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

Plan items

• 🏃 Contributions to the Python extension, see plan @karthiknadig team

---

Deferred Items

- [ ] 🏃‍♀️ Debug extension bugs; [query](https://github.com/microsoft/vscode-python-debugger/issues?q=is%3Aissue%20state%3Aopen%20assignee%3Aeleanorjboyd%20label%3Abug); @eleanorjboyd

• 🏃‍♀️ ✋ Contribute to the coverage.py package through surfacing branch coverage; issue; @eleanorjboyd

• 💪 Show "install Jupyter extension" only if users have rich output in REPL; issue; @anthonykim1

• Formalize Python project/packages structure and content for opinionated flow; issue; @cwebster-99 @karthiknadig

• ⬛ Create content for AI tutorial; issue; @cwebster-99 @luabud

• 💪 Support interrupt for Native REPL on Windows; issue; @anthonykim1

• 💪 Start refactoring code for custom args; issue; @eleanorjboyd

• 🏃 Add launch support for test discovery and execution in settings.json; issue @eleanorjboyd

• Unify venvPath and venvFolders; issue

• Switch to using unittest.main and a custom runner for unittest; issue; @eleanorjboyd

• Understand the problem for git pre-commit hooks; issue @anthonykim1

• 💪 Run in Python REPL for Chat; issue; @anthonykim1