On Mon, Nov 6, 2017 at 9:03 AM, vitalije <[email protected]> wrote:
> It is now clear that it's possible to create kernels without interacting >> with the Jupyter notebook server. In retrospect, Terry has likely been >> trying to tell me this for awhile... >> > > I believe it is quite opposite of what Terry has suggested. If I > understood well, Terry was suggesting interacting (sending and receiving > messages) with server, and leave kernels alone. Kernels should be server's > concern not Leo's. Server will create and deal with them upon receiving > message from Leo. Leo should not create directly kernels. Otherwise, Leo > will need to re-implement all code from server that is intended to deal > with kernels. > The problem we all have, I think, is that there appears to be no "how to" documents regarding jupyter clients, servers, kernels, sessions, etc. Please let me know if I have missed something. I have spent considerable time looking at the existing jupyter_client demo (__main__.py). I can see how the code handles the messages, but the init process is insanely complicated. I have no idea how to reuse the code. The jupyter_client demo creates a client, several sessions, and at least one kernel. Afaik, it does not create a stand-alone server, but I could be wrong. As I have said before, this project borders on being too complex for me to understand. I certainly do not understand how this could work with Leo. In my talk this morning with my friend Phil Straus, I said it is time for me to put this project on hold. There are many other tasks that I have neglected recently, and it's hard for me to justify this kind of speculative work. I would welcome any help you, Terry, or anyone else could give. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
