in order to create the notebook cell execution task controller is passed into IKernel constructor and then passed all the way down through the constructors of KernelExecution, CellExecutionQueue, CellExecution etc.

Our code currently assumes a 1-1 relationship between a VS Code NotebookController and our internal IKernel objects, i.e.

Currently vscode.NotebookControllers are per-notebookType, so to get our kernels to show up for interactive windows, each of our kernels is registered twice with VS Code–once for the jupyter-notebook notebookType and once for the interactive notebookType.

to be reused for an interactive controller that is selected for a given interactive NotebookDocument.

an IKernel that is currently mapped to a jupyter-notebook controller which has been selected for a given jupyter-notebook NotebookDocument.

Summary: Jupyter extension needs to refactor our VSCodeNotebookController wrapper, IKernel, and the cell execution codepath to allow.

Introduce keybinding or similar to copy code (otherwise user has to move mouse literally the entire span of the screen).

Should the scratchpad contain just the one cell (fully matching behavior) or be a full interactive window?.

Should users be able to start multiple interactive consoles? Original prototype has scratchpad singleton.

Should the interactive window immediately receive focus when created?.

Context keys to hide interactive window specific functionality.

Sys info cell to indicate the notebook association.

Command contributed to interactive/cell/title to paste code back into notebook.

Command contributed to notebook/cell/title to open interactive window connected to same kernel.

“…have an ability to launch an IPython shell (within VS Code) which is binded to the kernel of a specific notebook (so all objects defined in the notebook are accessible there etc.)…”.

The main usecase is to be able to work interactively based on the state of a notebook without having to tinker with the notebook itself.”

“…create interactive Python consoles connected to specific notebook kernels.

“…interactive command line that is connected to a jupyter notebook…”.

“I add some cells to try something out and I don’t want to lose them, but I don’t want them in my ‘main’ notebook.”.

Visual studio code jupyter notebook