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 in April. 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.
PyCon is at the end of the month. Looking forward to meeting some of you there!
🏃 Investigate a method to create or suggest a virtual environment with ipykernel + needed packages for a given notebook vscode-jupyter#9640@IanMatthewHuff
Engineering
Refactor the code base to group code with similar runtime requirements (node versus browser) vscode-jupyter#9267@rchiodo
Assume ownership of the Interactive Window @amunger
Release the Jupyter Powertoys extension to the public, with a clear story on expectations for how features will be added / removed vscode-jupyter#9251@IanMatthewHuff
🏃 Mitigate slow kernel discovery (API adoption, placeholder kernels, measurements) vscode-jupyter#9628@DonJayamanne - Python extension to investigate/implement a couple of changes next iteration (#'s TBD) to make interpreter discovery much quicker for Jupyter's use case.
This plan captures our work in April. 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.
PyCon is at the end of the month. Looking forward to meeting some of you there!
Plan Items
Below is a summary of the top level plan items.
Legend of annotations:
Jupyter Notebook High Priority
Jupyter Notebook Focus Areas
ipykernel
+ needed packages for a given notebook vscode-jupyter#9640 @IanMatthewHuffEngineering
Deferred
The text was updated successfully, but these errors were encountered: