Skip to content

Python: Iteration Plan for February 2025Β #24803

@kieferrm

Description

@kieferrm

This plan captures our work on the Python Extension in February 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
Summary for plan reading
  • @karthiknadig Create Project flow, and startup activation.
  • @eleanorjboyd Copilot integration, package installation, research notebook experience, and debug extension bugs.
  • @cwebster-99 Create Project flow spike
  • @anthonykim1 Terminal shell integration, Gitbash workspace folder issue

Environments

Terminal

REPL

N/A

Testing

N/A

Debugger

Engineering

N/A


Deferred Items - [ ] πŸ’ͺ cpython upstream fix to adjust terminal cursor to correct place; [issue](https://github.com/python/cpython/issues/126131); @anthonykim1 - [ ] πŸƒβ€β™€οΈ βœ‹ Contribute to the coverage.py package through surfacing branch coverage; [issue](https://github.com//issues/24193); @eleanorjboyd

Metadata

Metadata

Assignees

Labels

iteration-planPlan for the current iteration

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions