You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This plan captures our work on the Python Extension in June 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.
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
Implement new getting started experience in the walkthrough; issue; @cwebster-99
🏃🔵 Get better understanding of pain points related to Python mono repo experience; issue; @luabud@cwebster-99
🏃 Draft artifact for our approach to packaging; @cwebster-99
This plan captures our work on the Python Extension in June 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.
Legend of annotations
Getting started
Environments
N/A
Editing
N/A
LSP
N/A
Terminal
N/A
Debugging
[object Object]
showing up as a notification; @paulacamargo25Formatting
N/A
Linting
mypy
extension to usedmypy
; issue; @karthiknadigTesting
vscode.dev
N/A
Documentation
Engineering
Python community
package.metadata
parsing; PR; @brettcannonDeferred Items
.python-version
for pyenv; issue; @karrtikrconda run
when debugging (waiting on the conda team to give us the go-ahead to rely onconda run
so fundamentally); @paulacamargo25venvPath
andvenvFolders
; issueThe text was updated successfully, but these errors were encountered: