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

Getting started

• Draft artifact for our approach to packaging; issue; @cwebster-99

Environments

• 🏃 Investigate how to handle Create Environment when called with a preexisting environment; issue; @karthiknadig
• Get test suite passing on Codespaces issue; @anthonykim1
• 🏃 Investigate potential uses of the WASI build of CPython (and maybe MicroPython); issue; @cwebster-99

Editing

N/A

LSP

• Create pipeline templates for lsprotocol; issue; @karthiknadig

Terminal

• Bring back dedicated terminal usage to the Run button; issue @karrtikr

REPL

• ⬛ Investigate the state of REPL support in the extension; issue @anthonykim1

Debugging

• Implement configuration that prompts users for arguments; issue @paulacamargo25
• Investigate reported failures of attaching the debugger to a running process; issue @paulacamargo25
• 🏃‍♀️ Pre-release of debugger extension using debugpy 1.5.1; issue @paulacamargo25

Formatting

N/A

Linting

N/A

Testing

• 🏃‍♀️ Triage open testing issues post-rewrite; issue @eleanorjboyd
• Have pytest discovery continue in the face of errors; issue @eleanorjboyd

vscode.dev

N/A

Documentation

• 🏃 FastAPI tutorial; issue; @luabud @cwebster-99 @minsa110

API

• Create an npm types package for public extension API; issue @karrtikr

Engineering

• Move the dev container over to an MCR image; issue @anthonykim1

Python community

• Document dev process for WASI for CPython; @brettcannon
• ⬛ 🏃‍ Enriched/strict package.metadata parsing; PR; @brettcannon