-
-
Notifications
You must be signed in to change notification settings - Fork 99
Description
Hello all,
I have been working for a long time now on streamlining the way in
which a kernel communicates with a client in order to simplify that
communication from a developer perspective. I am at the stage where I
would like to have some users test the changes to make sure there are
no glaring bugs that I've introduced. I have changed a few parts of
the code base that may have broken some people's setup, but most
changes have been relegated to internal components that should not
have much of an effect from a user perspective.
The biggest user facing change is the introduction of
the jupyter-use-zmq variable which allows a user to specify if zmq is
a library that can be used for communicating with kernels. If that
variable is nil (the default depends on the value
of (locate-library "zmq")) then only notebook type connections can be
made to kernels, that is all kernel communication is relegated to
talking to some notebook server which gives access to the WebSocket of
a kernel. If that variable is non-nil then a direct connection to a
kernel can be made through ZMQ sockets.
So if there is anyone who is willing to give the next branch a test
spin I would greatly appreciate it. Thanks.