vscode-jupyter
vscode-jupyter copied to clipboard
microsoft
Support a notebook "scratch pad" and/or integrate interactive window experience for notebooks
This is similar to gather but without having to run gather.
Sometimes I'm working on a notebook and 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.
any updates on this?, this is a killer feature to be honest for every data scientist.
There was a hackathon project that implemented it but we haven't shipped that yet. It's waiting more up votes I think.
This isn't on our backlog (you can check the milestone to see if we plan to implement it soon).
would be great to have this feature. It's the only thing preventing me atm from using VSC for jupyter notebooks...
I'd love to have this feature!
philffm seems to have found a workaround, but I haven't been able to figure out how to implement the first step of getting the notebook kernel's URL in VScode. If someone could confirm the workaround it would be great.
The workaround is to use a 'remote' jupyter server. Essentially you start jupyter yourself on your local machine and then use that to run your kernels.
That allows you to change the kernel to an already running kernel on any notebook or interactive window.
The workaround is to use a 'remote' jupyter server. Essentially you start jupyter yourself on your local machine and then use that to run your kernels.
That allows you to change the kernel to an already running kernel on any notebook or interactive window.
Thank you. This indeed works, but I'm having to create a notebook externally and then connect both the VSCode notebook and the VSCode interactive window to that kernel. It's better than nothing, but gets cumbersome if one needs to run several notebooks at the same time (I routinely have 5-6 actively run notebooks at any given time). So the question is - how could one obtain the URL of the kernel of the notebook started within VSCode, i.e. internally? Then one could simply pass that URL on to the interactive window and voila.
So the question is - how could one obtain the URL of the kernel of the notebook started within VSCode, i.e. internally? Then one could simply pass that URL on to the interactive window and voila.
This isn't possible. There isn't one.
However you don't have to open the notebook outside VS code. If you set VS code to use 'remote' (localhost), just open a notebook and run it. The kernel should then appear in the list of kernels for an interactive window if you start it afterwards.
@ulfaslak It looks like Jupyter: Create Interactive Window do the job. Just switch the ipykernel in the top right corner manually.
@vuvalini Not in my environment. It creates and connects to a new kernel instance, not the existing one that my notebook runs on.
similar idea here: https://github.com/microsoft/vscode-jupyter/issues/6765
hello,
is any progress on this? I recently switched from jupyter lab to vscode, and this feature, aka "interactive ipython console attached to the notebook", is a must have feature. This is a very frequent thing, that I need to access variables, do some temporary plots or analytics, but I do not want then in the notebook.
Same question - any update on this - I would like to move to VS Code for Copilot, but looking for that feature:)
This hasn't yet made it into the plan and still relies on #6765, though still something that we plan to do.
Using a jupyter server created outside vs code is still a reliable workaround though https://github.com/microsoft/vscode-jupyter/issues/6484#issuecomment-1018674246
I got that working (a interactive window in VScode connected to the same kernel of the notebook) following these instructions https://stackoverflow.com/a/72599604/4752223
kernel of the notebook = a kernel running in JupyterLab server
Unfortunately, I was aiming to also be able to run just a notebook-selection (Shift+Enter) into that 'interactive window' (just like in Jupyterlab) but that seems not possible yet.
Running a separate jupyter server is a non-solution.
I work with several people who continue to avoid vscode because this feature is missing. I'm also pretty keen on it.
This hasn't yet made it into the plan and still relies on #6765, though still something that we plan to do.
Using a jupyter server created outside vs code is still a reliable workaround though #6484 (comment)
I have followed the steps in #6484. I create a server and copy and paste the server's URL into the interactive window's interpreter. It seems to work but as soon as I close the interactive window, the kernels shut down.
This works well in ipynb files, though. I can close the jupyter notebook, connect again, and continue using the same kernel.
Is there a way to prevent the interactive window from shutting down the kernel after closing it?
Is there a way to prevent the interactive window from shutting down the kernel after closing it?
unfortunately no, this by design
This hasn't yet made it into the plan and still relies on #6765, though still something that we plan to do.
Using a jupyter server created outside vs code is still a reliable workaround though #6484 (comment)
@Everyone What would it take for this feature request to make it to the plan? How does the team select and prioritize external feature requests?
