async-kernel

logo-svg

async-kernel provides Python Jupyter kernels and clients compatible with CPython (Jupyter & VS code) and Pyodide (Jupyterlite).

The kernel interface supports multiple connections including:

Messaging via ZMQ sockets (Jupyter, VS Code, etc).
Same-process local client (Jupyterlite).

Highlights

Built using aiologic thread-safe synchronisation primitives.
The Caller class provides a powerful but simple interface for cross-thread code execution in asyncio and trio backends, with guest event loop support built in.
A zmq poll event loop for thread-safe zmq sockets.
IPython shell
- top-level await (asyncio or trio backend) in cells
- async magic function support in cells
Per-subshell user_ns
GUI event loops ¹
- inline
- ipympl
- tk host and asyncio² or trio³ backend running as a guest
- qt host and asyncio² or trio³ backend running as a guest
Experimental support for Jupyterlite (try it online here 👈)
- %pip install magic (using micropip)
Debugger client
Local client.
ZMQ client.

Installation

pip install async-kernel

Kernelspecs

A kernelspec with the name 'async' is added when async-kernel is installed.

Kernel specs can be installed/uninstalled via the command line.

async-kernel install

# To install for a user
async-kernel install --user

For further detail about kernel spec customisation see command line and kernel configuration and custom kernel.ipynb.

Faster data serialization

orjson (a fast JSON library) is supported and will be used by default if it has been installed.

Free-threading support

async-kernel's Caller's are thread-local and it's methods are internally synchronised⁴.

Origin

async-kernel started as a fork of IPyKernel. Thank you to the original contributors of IPyKernel that made async-kernel possible.

A gui (host) enabled kernel interface starts a gui's mainloop (host) which starts the backend as a guest, then finally the Kernel is started. ↩
The asyncio implementation of start_guest_run was written by the author of aiologic and provided as a gist. ↩ ↩²
trio's start_guest_run. ↩ ↩²
free threading terminology ↩

Metadata

Release files for async-kernel 0.23.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for async-kernel 0.23.0
File	Size	Uploaded
async_kernel-0.23.0.tar.gz	375.6 kB	Sep 9, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for async-kernel 0.23.0
File	Interpreter	ABI	Platform	Reset
async_kernel-0.23.0-py3-none-any.whl 139.8 kB Sep 9, 2026	Python 3	none	any	Details

Total release size: 515.3 kB

Release files / async_kernel-0.23.0.tar.gz

Download URL	async_kernel-0.23.0.tar.gz
Size	375.6 kB
Tags	Source
SHA-256 checksum How to use checksums	`d1517159a63d21ad617f80195dd17e4cbce910f287dd8e6876e50afaa88bdb08`
BLAKE2b-256 checksum How to use checksums	`a1ed6c421556b78c94b0e9044165b1608bd8a098841ae4706669f854f1af0eeb`
Upload date	Sep 9, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/fleming79/async-kernel
Publishing commit: github.com/fleming79/async-kernel/tree/a58847b1895397d8cc0141922e36e76c3411fdf6

Workflow

Publishing configuration: github.com/fleming79/async-kernel/blob/a58847b1895397d8cc0141922e36e76c3411fdf6/.github/workflows/publish-to-pypi.yml
Publishing logs: github.com/fleming79/async-kernel/actions/runs/34326588375/attempts/1

Artifact

Subject: async_kernel-0.23.0.tar.gz
SHA-256 checksum: d1517159a63d21ad617f80195dd17e4cbce910f287dd8e6876e50afaa88bdb08 Verifying attestations

Release files / async_kernel-0.23.0-py3-none-any.whl

Download URL	async_kernel-0.23.0-py3-none-any.whl
Size	139.8 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`ab2895b425a09640a06e4265d1ffdd142bd94f1893af39198bd28525f95cc550`
BLAKE2b-256 checksum How to use checksums	`054952e90fcac5b6be88f050bb90ef1fa1761e63bcb54784b1d7240f24f824f4`
Upload date	Sep 9, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/fleming79/async-kernel
Publishing commit: github.com/fleming79/async-kernel/tree/a58847b1895397d8cc0141922e36e76c3411fdf6

Workflow

Publishing configuration: github.com/fleming79/async-kernel/blob/a58847b1895397d8cc0141922e36e76c3411fdf6/.github/workflows/publish-to-pypi.yml
Publishing logs: github.com/fleming79/async-kernel/actions/runs/34326588375/attempts/1

Artifact

Subject: async_kernel-0.23.0-py3-none-any.whl
SHA-256 checksum: ab2895b425a09640a06e4265d1ffdd142bd94f1893af39198bd28525f95cc550 Verifying attestations