This plan captures our work in September. 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 Create Environment command for extensibility; issue; @karthiknadig;
• Implement a Create Environment command; issue; @karthiknadig
• Expose interpreter quickpick API with filtering; issue; @karrtikr

Environments

• Work on finalizing design of proposed API for environments; issue; @karrtikr

Editing

None

LSP

• ⬛ Help pygls migrate to lsprotocol; discussion, PR; @karthiknadig

Terminal

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

Debugging

• Remove dependency injection from debugger code @paulacamargo25 @karthiknadig
  • Remove DI from debug configuration providers. issue
  • 🏃‍ Remove DI from debug configuration resolvers. issue
  • Remove DI from debug adapter factory. issue
  • 💪 Remove DI from launch and attach classes for testing. issue
  • 💪 Simplify launch and attach classes for testing. issue
• ✋ Isolate debugger code in core extension so it can be extracted easily; 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

Testing

• 🏃‍♀️ ⬛ Rewrite pytest execution/discovery through a pytest plug-in; issue; @eleanorjboyd @karthiknadig

(github|vscode).dev

None

Documentation

None

Engineering

None

Python community

• Participate on GHC OSD; issue @luabud @karthiknadig