#jupyter #token #pair #remote-server

jupyter-websocket-client

Connect to Jupyter Servers over WebSockets

12 releases (breaking)

new 0.11.0 Apr 30, 2025
0.9.0 Jan 9, 2025
0.8.0 Dec 2, 2024
0.6.0 Nov 28, 2024

#75 in WebSocket

Download history 3398/week @ 2025-01-10 2098/week @ 2025-01-17 2157/week @ 2025-01-24 2284/week @ 2025-01-31 2302/week @ 2025-02-07 2899/week @ 2025-02-14 2783/week @ 2025-02-21 3022/week @ 2025-02-28 2855/week @ 2025-03-07 3093/week @ 2025-03-14 2686/week @ 2025-03-21 2942/week @ 2025-03-28 2491/week @ 2025-04-04 531/week @ 2025-04-11 111/week @ 2025-04-18 211/week @ 2025-04-25

3,862 downloads per month

BSD-3-Clause

135KB
2.5K SLoC

jupyter-websocket-client crate

Note: This crate does not support tokio at this time.

Usage

use jupyter_websocket_client::RemoteServer;

use jupyter_protocol::{KernelInfoRequest, JupyterMessageContent};

// Import the sink and stream extensions to allow splitting the socket into a writer and reader pair
use futures::{SinkExt as _, StreamExt as _};

pub async fn connect_kernel() -> anyhow::Result<()> {
    let server = RemoteServer::from_url(
        "http://127.0.0.1:8888/lab?token=f487535a46268da4a0752c0e162c873b721e33a9e6ec8390"
    )?;

    // You'll need to launch a kernel and get a kernel ID using your own HTTP
    // request library
    let kernel_id = "1057-1057-1057-1057";

    let kernel_socket = server.connect_to_kernel(kernel_id).await?;

    let (mut w, mut r) = kernel_socket.split();

    w.send(KernelInfoRequest {}.into()).await?;

    while let Some(response) = r.next().await.transpose()? {
        match response.content {
            JupyterMessageContent::KernelInfoReply(kernel_info_reply) => {
                println!("Received kernel_info_reply");
                println!("{:?}", kernel_info_reply);
                break;
            }
            other => {
                println!("Received");
                println!("{:?}", other);
            }
        }
    }

    Ok(())
}

Dependencies

~8–20MB
~286K SLoC