Closed
Description
This plan captures our work in July. 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.
Plan Items
Below is a summary of the top level plan items.
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 |
Notebooks
- 🔴 Switch all users over to use VS Code built-in notebooks @claudiaregio
- Bring plot viewer support to built-in notebooks vscode-jupyter#6315 @DonJayamanne
- 🏃 Support run by line vscode-jupyter#5607 @DavidKutu @roblourens
Interactive Window
- Address all issues blocking the built-in interactive window from being the default https://github.com/microsoft/vscode-jupyter/blob/main/.vscode/notebooks/jupyter.github-issues @joyceerhl @rebornix @rchiodo
- 💪 Explore using the interactive window as a console for notebook kernels vscode-jupyter#6765 @joyceerhl @rebornix
Documentation
- 🔴 Update documentation to use built-in notebooks @claudiaregio team
- 🔴 Move documentation to
https://code.visualstudio.com/docs@claudiaregio @gregvanl
Engineering
- 🔴 💪 🏃 Simplify Code clean-up/simplification in the Jupyter extension @greazer team
- 🔴 💪 Explore separating the default output renders into their own extension @greazer team
Deferred
- Placeholder kernel to ensure run button appears immediately in a notebook vscode-jupyter#5861 @DonJayamanne
- Add telemetry to get perf times for loading python & non-python kernels for the first time (without cache)
- Discuss with Python team to improve perf around discovering Python interpreters