16

I am able to connect two ipython console session to one kernel by: 

$ ipython console
In [1]: %connect_info  
{
   ... Content of JSON with info for connecting ...
}

Paste the above JSON into a file, and connect with:
    $> ipython <app> --existing <file>
or, if you are local, you can connect with just:
    $> ipython <app> --existing kernel-43204.json
or even just:
    $> ipython <app> --existing
    if this is the most recent IPython session you have started.

And accordingly I can substitute the <app> by console again

$ ipython console --existing kernel-43204.json

However, I want to share my kernel with ipython notebook so I can visualize my data. I tried and failed with:

$ ipython notebook --existing kernel-43204.json
[C 13:35:01.025 NotebookApp] Unrecognized flag: '--existing'

Any suggestion how I can work and switch between ipython console and ipython notebook?

Oplatek
  • 343
  • 2
  • 13

3 Answers3

9

There is no UI, nor API to do that with the notebook, there is an assumption for code simplicity that the notebook is the one that own and start the kernel. You will have to write your own KernelManager subclass and configure IPython to use it (+ write a bit of UI code, if you want it easy to use), for you to be able to select an already existing kernel.

Matt
  • 26,019
  • 6
  • 79
  • 73
  • Do you think that this not implemented feature is against the ipython notebook "ideology"? ... or it may become maintained if implemented? – Oplatek Jul 15 '15 at 17:32
  • I doubt it would be maintained if implmented, there are some inherent abstraction breakage if you do that. Though is a limited fashion, I know that it would be interesting for some people. – Matt Jul 15 '15 at 23:00
  • So, if I understand, notebook allows multiple kernel instances (one per notebook), and multiple kernel types (Kernel->Change Kernel menu), but all kernels must be initiated from the HTML interface. Since the kernel ZeroMQ interface has some security, I was hoping to run the kernel-only on a shared server machine and attach locally running notebook to the existing kernel. Motivated by no solution to this [question](http://stackoverflow.com/questions/32914669/can-an-http-server-listening-on-localhost-be-made-accessible-to-just-one-user). I'm overwhelmed by the steps to configure HTTPS. – NoahR Oct 08 '15 at 21:11
  • Another use case for Jupyter notebooks to support connecting to an already running kernel is to aid in debugging the kernel itself. As it is currently not possible to launch a kernel in a debugger and then have Jupyter notebook connect to that kernel instance being debugged, we have to resort to having Jupyter launch the kernel, then attach a debugger to this already running kernel. This means that it is very difficult if not impossible to debug early kernel startup unless we modify the kernel to somehow wait for a debugger to attach to it. – ack Mar 18 '21 at 16:22
1

Here’s the example of custom kernel manager that allows Jupyter notebook to kernel created externally.

https://github.com/ebanner/extipy

It’s hacky solution at best.

Jupyter folks can hopefully create such custome kernel class and include it in package and enable it via simple —existing switch. I don’t see any reason why they can’t do that.

Shital Shah
  • 55,892
  • 12
  • 218
  • 175
1

I'll give you a solution the other way around. Instead of connecting a notebook to an existing kernel, you can easily connect an ipython session to a kernel that was started by a notebook.

  1. Start your notebook. Now you have a running kernel.
  2. In a code cell, run the magic command %qtconsole

Now you have a console and the notebook connected to the same kernel. You can run the magic command multiple times and have multiple consoles.

BTW, qtconsole is a very smart console. It is even better than the terminal one, especially if you are a Windows user.

neves
  • 26,235
  • 24
  • 129
  • 157