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

Getting started

• 🏃‍♀️ Investigate creating template repos for various project types; issue; @cwebster-99

Environments

• 🏃‍♀️ ⬛ Implement Environments view UI (aka Don's environment extension); issue; @karthiknadig
  • 🏃‍♀️ ⬛ Native locator for globally installed python and virtual environments; issue; @karthiknadig @DonJayamanne
• 🏃‍♀️ Gather feedback on environments panel UI; issue; @cwebster-99 @karthiknadig
• 💪 Formalize Python project/packages structure and content for opinionated flow; issue; @cwebster-99 @karthiknadig

Editing

N/A

Terminal

• 💪 Add other shell types to core; issue; @anthonykim1

REPL

• Spike to find common ground between Python REPL and IW; issue; @anthonykim1 @amunger
• built-in Python REPL implementation issue @anthonykim1 @amunger

Debugging

• Improve "Run and debug" button support; issue; @paulacamargo25
• Investigate a debug terminal with shell integration; issue; @paulacamargo25
• Investigate dynamically detecting production, staging, and development configurations for Django; issue; @paulacamargo25

Testing

• Address pytest dicovery failure with ENOENT; issue @eleanorjboyd
• 🏃‍♀️ Dynamically handle test framework on activation; issue; @eleanorjboyd
• 🏃‍♀️ Plan custom args user study; issue; @eleanorjboyd @cwebster-99 @paulacamargo25

vscode.dev

N/A

Documentation

N/A

API

N/A

Engineering

N/A

Python community

• PyCon US planning; @dawnwages
• Prepare for PyCon LSP booth presentation; @karthiknadig
• PyCon remote; @eleanorjboyd @anthonykim1