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 for April 2022 #18850

Closed
10 of 30 tasks
kieferrm opened this issue Apr 3, 2022 · 0 comments
Closed
10 of 30 tasks

Python: Iteration Plan for April 2022 #18850

kieferrm opened this issue Apr 3, 2022 · 0 comments
Assignees
Labels
iteration-plan Plan for the current iteration

Comments

@kieferrm
Copy link
Member

kieferrm commented Apr 3, 2022

This plan captures our work in April. 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

  • πŸƒβ€β™€ Create the WWBD extension w/ an opinionated flow for environment creation and requirements installation; @brettcannon

Environments

Editing

LSP

  • πŸƒβ€β™€οΈ Create a programmatic definition of LSP; issue; @karthiknadig
  • βœ‹ Explore pygls adopting programmatic definition of LSP (for notebook support); issue; @karthiknadig

Terminal

Debugging

  • ${env:...} variables are not being passed via launch.json; issue; @paulacamargo25
  • πŸƒβ€β™€οΈ πŸ”΅ Investigate automatic debug configuration based on the open workspace; issue; @paulacamargo25

Formatting

Linting

None

Testing

(github|vscode).dev

None

Documentation

None

Engineering

Python community


Deferred Items
  • Investigate environment detection in our overall environment UX to see if there are scenarios where discovery is unnecessary
  • Separate environment discovery into a two phases, "raw" and "enriched", so Jupyter can consume the former ASAP
  • βœ‹ πŸ”΅ Work w/ Pylance on automatic indentation vscode-python#481 @brettcannon (blocked on VS Code issue)
  • βœ‹ Create platform-specific VSIXs (blocked on standardizing on extension pipelines supporting platform-specific VSIXs); vscode-python#17439 @paulacamargo25
  • Infer environment variables for an activated conda environment vscode-python#17332 @karrtikr
  • Rewrite test discovery for pytest vscode-python#17242 @kimadeline
  • Rewrite test execution for unittest
  • Rewrite test execution for pytest
  • Start work on implementing packaging.metadata; issue; @brettcannon
@kieferrm kieferrm added the iteration-plan-draft Proposed plan for the upcoming iteration label Apr 3, 2022
@kieferrm kieferrm added this to the April 2022 milestone Apr 3, 2022
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Apr 3, 2022
@kieferrm kieferrm removed the triage-needed Needs assignment to the proper sub-team label Apr 3, 2022
@kieferrm kieferrm added triage-needed Needs assignment to the proper sub-team and removed triage-needed Needs assignment to the proper sub-team labels Apr 3, 2022
@kieferrm kieferrm pinned this issue Apr 3, 2022
@brettcannon brettcannon changed the title Python: Iteration Plan for April 2022 [DRAFT] Python: Iteration Plan for April 2022 Apr 4, 2022
@brettcannon brettcannon added iteration-plan Plan for the current iteration and removed iteration-plan-draft Proposed plan for the upcoming iteration labels Apr 4, 2022
@karthiknadig karthiknadig removed this from the April 2022 milestone Apr 28, 2022
@kimadeline kimadeline unpinned this issue May 31, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 5, 2022
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

3 participants