Open BoPeng opened 7 months ago
Any updates?
Not really. The interfaces with JupyterLab contains a few JS function to interact with the frontend and does not work here. We may need to develop a pure text-based interface similar to how we implement sos-papermill, but it is hard to justify the effort.
Any updates? And i will be appriciated if you can provide more details about how to use the sos kernel through the vscode interface.
There is no way to get the language dropdown there, which can be overcome by using the %use
magic more often. A more serious problem, however, is that (as far as I can tell) there is no way to know the kernel of the current cell, so it will always use the current kernel to execute the cell. This means all cells need to start with a %use
magic to make sure the right kernel will be used.
Let me see if I can find some time to have a deeper look at the issue.
In theory this should be feasible as the VSCode Polyglot Notebooks extension does something like this.
VSCode Polyglot Notebook is a totally different beast and it needs .NET installed locally (for my macOS X anyway).
Unless someone who is familiar with VSCode can point out what would be need to add that .NetIneractive button on VSCode/Jupyter, there is no way we can make sos notebook work with vs code.
Installed vscode jupyterhub extension, connected to our jupyterhub server, created a jupyter notebook with sos kernel. Unfornately, the kernel does seem to work correctly.
Note that sos notebook could be executed in batch mode and we have magics such as
%use
to manually change subkernels of cells, so in theory using the sos kernel through the vscode interface can be made to work.