| [ease-dev] Jupyter kernels |
Hi,
I've been working on launcher strategies for the EASE Jupyter kernels this week.
The flow for launching Jupyter kernels is basically the opposite of what we want. To launch a new kernel, an executable is called with command line parameters, the most important of which specify the ports that will be used for communication. We would like to tell Jupyter which ports we are using as to have more control and be more customizable from within eclipse.
I currently do not see an easy solution to this problem, so I decided to simply create a command line tool that will be called by Jupyter and dispatches the parameters over a socket to a running eclipse instance. This strategy has some downsides, the most obvious being that with this simple solution we can only have one eclipse instance running at a time.
I would still like to keep this method for now as it allows me to continue with the actual implementation of the kernels. In the future it would be possible to dynamically add running eclipse instance to Jupyter using the same method but with different dispatching ports for each. This code would not be platform independent as Jupyter has different locations for its kernel information on each OS.
Does anyone of you know of a better solution to this problem?
Besides working on this topic, Tobias from the Science working group has given me his code regarding Jupyter clients in eclipse. I have been checking the code and it looks as if I could reuse some of it for the kernels as well (mostly zmq messaging). You can check out his code at:
https://github.com/openanalytics/japyter
https://github.com/openanalytics/jupyter-console
Thanks again to him and the guys from the Science working group for the great collaboration. I think this project can help both teams and get EASE and eclipse even further...
Best regards,
Martin