Python: Iteration Plan for August 2022

[kieferrm]

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

• Come up with a plan about how to decide what a Getting Started flow ala WWBD should be like; issue; @brettcannon

Environments

• 🏃‍♀️ Work on finalizing design of proposed API for environments; issue; @karrtikr

Editing

None

LSP

• Convert lsprotocol to snake case; issue; @karthiknadig

Terminal

• Explore options for activated terminals and terminal profiles vscode-python#11039 @luabud @karrtikr

Debugging

• 🏃‍ Create a plan to break out debugging support into it's own extension; issue @paulacamargo25 @karthiknadig

Formatting

• Control rollout of notifying about the Black extension; issue ; @luabud @karthiknadig
• Control rollout of notifying about the isort extension; issue; @luabud @karthiknadig
• 🏃‍♀️ Publish an autopep8 extension; issue; @karthiknadig

Linting

• Control rollout of notifying about the Pylint extension; issue; @luabud @karthiknadig
• Publish a flake8 extension; issue; @karthiknadig

Testing

• Rewrite unittest execution code; issue; @ksy7588 @karthiknadig
• 🏃‍♀️ Investigate how to do pytest execution/discovery via plug-in; issue; @ksy7588 @karthiknadig

(github|vscode).dev

None

Documentation

None

Engineering

• ✋ Write web tests; issue; @karthiknadig

Python community

• Write down a plan for what needs to happen for healthy support for WASI; issue; @brettcannon

---

Deferred Items

• ✋ 🔵 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 pytest
• ✋ Start work on implementing packaging.metadata; issue; @brettcannon
• ✋ Finalize Python Launcher plug-in design (blocked on conda's feedback); discussion; @brettcannon
• Support .python-version for pyenv; issue; @karrtikr
• Investigate any remaining places we are not using conda run
• Implement a Python traceback problem matcher in core
• 🔴 Use conda run when debugging (waiting on the conda team to give us the go-ahead to rely on conda run so fundamentally); @paulacamargo25
• Provide settings to control what environment details are displayed; @karrtikr
• Investigate configuring running and debugging