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
Environments
N/A
Editing
N/A
LSP
N/A
Terminal
N/A
Debugging
Formatting
N/A
Linting
Testing
vscode.dev
N/A
Documentation
Engineering
Python community
Deferred Items
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
mypyextension to usedmypy; issue; @karthiknadigTesting
vscode.devN/A
Documentation
Engineering
Python community
package.metadataparsing; PR; @brettcannonDeferred Items
.python-versionfor pyenv; issue; @karrtikrconda runwhen debugging (waiting on the conda team to give us the go-ahead to rely onconda runso fundamentally); @paulacamargo25venvPathandvenvFolders; issue