yeptris — YAML for Python at libleptris speed
An FFI-based (no C extension) YAML library over libyeptris — the YAML counterpart of libleptris. PyYAML-compatible semantics, one shared library, zero compilation at install.
Install (development)
# the sibling C checkout: ~/src/leptris/yeptris
cmake -B build -S . -DCMAKE_BUILD_TYPE=Release -DYEPTRIS_BUILD_SHARED=ON
cmake --build build
cd ~/src/leptris/yeptris-py
YEPTRIS_LIB_PATH=../yeptris/build/src/libyeptris.dylib python3 -m pytest
Without YEPTRIS_LIB_PATH the loader falls back to a vendored
yeptris/_platform/<tag>/ copy, then to the sibling checkout's
build directory. Any libyeptris.{so,dylib,dll} path works.
Usage
import yeptris
from yeptris import yaml # PyYAML-compatible surface
yaml.safe_load("name: yeptris\nrating: 10\n")
# {'name': 'yeptris', 'rating': 10}
yaml.safe_load_all("--- 1\n--- two\n") # [1, 'two']
yaml.safe_dump({"b": 2, "a": [1, "x"]}) # 'a:\n - 1\n - x\nb: 2\n'
yeptris.load("k: v") # the neutral surface
yeptris.dump({"k": [1, 2]})
Typing follows PyYAML's SafeLoader (YAML 1.1 implicit typing):
yes/no/on/off booleans, 0x/leading-0/0b/sexagesimal integers,
dot-required floats, timestamps with offsets, merge keys, anchor
identity. Every deliberate divergence is pinned by a test.
Design
One parse, one bulk drain: the record array and string arena are
read in two FFI calls, then a pure-Python walk over the unpacked
records — the FFI tax is O(1) per document, never per event (the
same seam yeptris-ruby rides). The 36-byte record layout is
ABI-pinned in the C header and mirrored in _ffi.py.
Performance
python3 bench.py — same-process comparison against PyYAML (pure)
and CSafeLoader/CDumper (libyaml C extensions):
- load: 28-39x PyYAML pure, 3.8-6.1x CSafeLoader
- dump: ~1.7x PyYAML pure, ~2x behind CDumper (which walks the
tree entirely in C — a no-C-extension design's ceiling is the
Python walk itself; the tree raises through ONE
yeptris_document_buildcall)
Both directions are O(chunks) in FFI calls: loads drain records in two calls, dumps build through one flat entry array.
JSON (strict RFC 8259) — yeptris.json
yeptris.json.loads is json.loads-compatible (values, rejects,
types, json.JSONDecodeError — including stdlib's default NaN/
Infinity constant quirk) with two engines behind one contract:
- native — the opt-in extension
ext/yeptris_native.c: a fused scan-kernel descent over libyeptris (the same shape as the Ruby binding's materializer), with a 1024-slot interned-free key cache. Build it withYEPTRIS_LIB_PATH+YEPTRIS_SRCset (python3 setup.py build_ext --inplace); CI builds and gates it. - strict-ffi — the default pure path:
yeptris_parse_jsonis the validator gate, then the columnar value walk converts under JSON rules. No C extension, correct everywhere.
benchmark/json_profile.py is the referee (order-alternating
interleave vs the C scanner): the native engine runs 0.67-0.87x
json.loads mean (83-85% head-to-head) on the 144 KB reference
corpus; shape decomposition: int arrays 0.63x, float arrays 0.77x,
long strings 0.85x, unique-key maps 0.95x. The previous pure walk
was ~15x BEHIND — the fused materializer is the entire gap.
Installing the native JSON engine (platform wheels)
pip install yeptris on macOS (arm64) and manylinux (x86_64)
installs platform wheels that vendor libyeptris and the native
JSON materializer (abi3 — one wheel per platform serves CPython
3.9+): zero compiler, zero env vars, yeptris.json.engine() is
native out of the box. Every wheel is release-smoked in a clean
venv before publish. Other platforms install the pure package (the
strict-ffi JSON engine + YAML via libyeptris through the
YEPTRIS_LIB_PATH ladder); building the extension from source is
YEPTRIS_LIB_PATH=... YEPTRIS_SRC=... python3 setup.py build_ext --inplace.
1 maintainer
Release files for yeptris 0.3.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| yeptris-0.3.0.1.tar.gz | 24.9 kB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| yeptris-0.3.0.1-py3-none-any.whl | Python 3 | none | any | Details |
| yeptris-0.3.0.1-cp39-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| yeptris-0.3.0.1-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| yeptris-0.3.0.1-cp39-abi3-macosx_11_0_x86_64.whl | CPython 3.9 | abi3 | macOS 11.0+ x86-64 | Details |
| yeptris-0.3.0.1-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details |
Total release size: 1.1 MB
Release files / yeptris-0.3.0.1.tar.gz
| Download URL | yeptris-0.3.0.1.tar.gz |
|---|---|
| Size | 24.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d06e75fbb49e508841594971d46f4536dd693d74cd54dce6b1d7b5f9994e8a35
|
|
BLAKE2b-256 checksum How to use checksums |
afcf3db507757d3f7fed4be357063bf85abf5c8d72fcf23754906aaba3fe5523
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.5
|
Release files / yeptris-0.3.0.1-py3-none-any.whl
| Download URL | yeptris-0.3.0.1-py3-none-any.whl |
|---|---|
| Size | 18.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9831ff54999d6995e2e3fd2d19125a38f153269cc6b241f7fe94776396696cb0
|
|
BLAKE2b-256 checksum How to use checksums |
f541da47cc8c73029504445cd17068849b644ac63312f4b0102cdd500998b9f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.5
|
Release files / yeptris-0.3.0.1-cp39-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | yeptris-0.3.0.1-cp39-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 290.9 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
27a4d58241465ce0fef6af00b137beecf6817297ae8663e7163de5c52a3c2caf
|
|
BLAKE2b-256 checksum How to use checksums |
9f52277da33038d1532d23fa879b3e0e6c7acfa21d2f4ccdb480172898a25cfd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.5
|
Release files / yeptris-0.3.0.1-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | yeptris-0.3.0.1-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 293.5 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
04413fb368462fc0c0f0f1f363e7c7f73008d66b636a1f645f1060ee72fc1211
|
|
BLAKE2b-256 checksum How to use checksums |
053cdf66a0d93424326454c8851011e5aa0a8cd282a2affb81972bffaffa2a86
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.5
|
Release files / yeptris-0.3.0.1-cp39-abi3-macosx_11_0_x86_64.whl
| Download URL | yeptris-0.3.0.1-cp39-abi3-macosx_11_0_x86_64.whl |
|---|---|
| Size | 257.8 kB |
| Tags | CPython 3.9 abi3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
864867f8bafbe006fe173cfbc754834a29b60e5f11083678f4e7b95430fabcb8
|
|
BLAKE2b-256 checksum How to use checksums |
8c59f4741395a88f69ee50ee99ea65938d6e62abb5e2b8fd76e38d74c2bcda83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.5
|
Release files / yeptris-0.3.0.1-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | yeptris-0.3.0.1-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 246.5 kB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
10089843e6748b3e3e66bfd3333c3931ea218c476c3bddd59671ca241b78b620
|
|
BLAKE2b-256 checksum How to use checksums |
d247ffe226e6a85cff2a5040fa5f4855f72b43dc5e878a095435b6858dd95551
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.5
|
