Day 56 — The littlest Jupyter console27 October 2020 · recurse-center Tweet
This week I'm planning to build a terminal frontend for Jupyter (in Rust!) so today I started looking into how Jupyter works!
The kernel exposes some sockets, using which the
jupyter_console "frontend" can communicate with the kernel (the "backend"). A single kernel can simultaneously be connected to multiple frontends.
These are the sockets that the kernel exposes:
- Shell: This is the socket where a frontend sends requests for executing code, among other things.
- IOPub: This is the socket where the kernel publishes "side effects" such as printing execution results to
stdout, printing error tracebacks to
- stdin: This socket is connected to all frontends and lets the kernel request input from "the active frontend".
- Control: This socket is used to send shutdown and restart messages to the kernel, and other kernel management messages.
- Heartbeat: This socket is used for monitoring the kernel's heartbeat to check if the frontend and the kernel are connected or not.
I thought that it might be fun to implement and see what the littlest (read "barely functioning")
jupyter_console would look like! And came up with something which has the following limitations (and more that I can't list down right now):
- Assumes that there's only one frontend session active at any given time
- Supports only backspaces for editing code! (no arrows keys or tabs :( )
- Executes only one line of code (
\tcan be added though!)
- Only reads messages from the IOPub channel
- Does not store code history!
It works (barely)! I want to call it
In : import os In : print(os.getcwd()) /home/vinayak/dev In :
Now I need to understand how
zeromq works; and implement,
client.iopub_channel.get_msg() in Rust! And also figure out how to start a Python kernel from Rust.