Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python: Iteration Plan forJuly 2024 #23749

Closed
20 of 25 tasks
kieferrm opened this issue Jul 7, 2024 · 0 comments
Closed
20 of 25 tasks

Python: Iteration Plan forJuly 2024 #23749

kieferrm opened this issue Jul 7, 2024 · 0 comments
Assignees
Labels
iteration-plan Plan for the current iteration

Comments

@kieferrm
Copy link
Member

kieferrm commented Jul 7, 2024

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

N/A

Environments

Editing

N/A

Terminal

REPL

Debugging

Testing

vscode.dev

N/A

Documentation

API

N/A

Engineering

N/A

Python community

  • 🏃‍♀️ Proof of concept for lock file PEP; @brettcannon
  • Make sure CPython works with latest release of wasmtime; @brettcannon
  • Make sure CPython works with the latest release of WASI SDK; @brettcannon

Deferred Items - [ ] Formalize Python project/packages structure and content for opinionated flow; [issue](https://github.com/microsoft/vscode-python-internalbacklog/issues/472); @cwebster-99 @karthiknadig - [ ] DjangoCon Europe - Supercharge Python DX in VS Code, Codespaces and Dev Containers Workshop; @dawnwages - [ ] EuroPython / SciPy planning; @dawnwages @luabud - [ ] 💪 Leverage variable pane in Native REPL; [issue](https://github.com//issues/23568); @anthonykim1 @amunger - [ ] Remove old testing code; [issue](https://github.com//issues/23569); @eleanorjboyd - [ ] 🔵🏃‍♀️ Adopt proposed API for testing coverage feature; [issue](https://github.com//issues/22671); @eleanorjboyd - [ ] 💪 Start refactoring code for custom args; [issue](https://github.com//issues/22670); @eleanorjboyd - [ ] 🏃‍♀️ ⬛ [Implement a dependency resolver with a customizable API](https://github.com/brettcannon/mousebender/issues/105); @brettcannon - [ ] 🏃 Add launch support for test discovery and execution in `settings.json`; [issue](https://github.com//issues/21845) @eleanorjboyd - [ ] Unify `venvPath` and `venvFolders`; [issue](https://github.com//issues/1479)
@kieferrm kieferrm added the iteration-plan-draft Proposed plan for the upcoming iteration label Jul 7, 2024
@kieferrm kieferrm added this to the July 2024 milestone Jul 7, 2024
@kieferrm kieferrm changed the title Python: Iteration Plan forJuly 2024 [DRAFT] Python: Iteration Plan forJuly 2024 Jul 9, 2024
@kieferrm kieferrm added iteration-plan Plan for the current iteration and removed iteration-plan-draft Proposed plan for the upcoming iteration labels Jul 9, 2024
@karthiknadig karthiknadig removed this from the July 2024 milestone Jul 23, 2024
@kieferrm kieferrm closed this as completed Aug 4, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
iteration-plan Plan for the current iteration
Projects
None yet
Development

No branches or pull requests

2 participants