Python: Iteration Plan for April 2025 #24969
Assignees
Labels
iteration-plan
Plan for the current iteration
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This plan captures our work on the Python Extension in April 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
Plan items
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 @eleanorjboydUnify
venvPathandvenvFolders; issueSwitch to using
unittest.mainand a custom runner for unittest; issue; @eleanorjboydUnderstand the problem for git pre-commit hooks; issue @anthonykim1
💪 Run in Python REPL for Chat; issue; @anthonykim1
The text was updated successfully, but these errors were encountered: