updated: 2025-12-05T17:41:33.976811096-08:00[America/Los_Angeles]

README

ry

A growing collection of Python shims around Rust crates; fast, async-first, and ergonomic.

DOCS: ryo3.dev (WIP)

API: ryo3.dev/api

This is a work in progress ~ feedback and PRs are welcome.

Async-first HTTP client: Built on reqwest, with a fetch-like API. Supports streaming, zero-copy IO via the buffer protocol, timeouts, redirect-following, and native JSON parsing via jiter.
Async file I/O: Built on tokio, with an AsyncFile API similar to aiofiles and anyio’s async-file api. Supports buffered reads/writes, truncation, streaming reads, and anyio compatibility.
(de)compression: (de)compression tools for zstd, brotli, gzip, and bzip2.
Datetime utilities via jiff: Fast, accurate, timezone-aware datetime parsing and formatting, with datetime interop and much more
Miscellaneous bindings: Includes crates like globset, walkdir, sqlformat, unindent, twox-hash, and more.
Designed for ergonomics: Async where it matters. Simple where possible. Python-native behavior with minimal friction.
Type Annotated: All public APIs are (painstakingly) type annotated.
Performant: Speed without the words “blazingly fast.” ¹

pip install ry
uv add ry

# check install
python -m ry

Check out the examples directory for some quickstart examples.

ry – the python package
ryo3-* – the rust crates that are used by ry and possibly your own pyo3-based python package

(aka: questions that I have been asking myself)

Q: Why?
- A: I (jesse) needed several hashing functions for python and then kept adding things as I needed them
Q: Does this have anything to do with the (excellent) package manager rye?
- A: short answer: no. long answer: no, it does not.
Q: Why is the repo split into ry and ryo3?
- A: ry is the python package, ryo3 is a rust crate setup to let you “register” functions you may want if you were writing your own pyo3-python bindings library; maybe someday the ryo3::libs module will be split up into separate packages