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.4.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.4.0.1.tar.gz | 24.9 kB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| yeptris-0.4.0.1-py3-none-any.whl | Python 3 | none | any | Details |
| yeptris-0.4.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.4.0.1-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| yeptris-0.4.0.1-cp39-abi3-macosx_11_0_x86_64.whl | CPython 3.9 | abi3 | macOS 11.0+ x86-64 | Details |
| yeptris-0.4.0.1-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details |
Total release size: 1.2 MB
Release files / yeptris-0.4.0.1.tar.gz
| Download URL | yeptris-0.4.0.1.tar.gz |
|---|---|
| Size | 24.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c38729697c3a5aa09bd207862513b2446de1d0f763bc55388f5f3ea6db4ae742
|
|
BLAKE2b-256 checksum How to use checksums |
c48191f9f70df8d5f91d74c48a547f3c2a693f08fab7b23ccab565c906e5e4db
|
| 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.4.0.1-py3-none-any.whl
| Download URL | yeptris-0.4.0.1-py3-none-any.whl |
|---|---|
| Size | 18.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9af10d716aa489ec0e953c87b1c7a54a79641b440f9393a75ee73da2988a4577
|
|
BLAKE2b-256 checksum How to use checksums |
3c619598504919711f4d7cb894542d91b83cbb4b303449a534de3e441b2d96ef
|
| 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.4.0.1-cp39-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | yeptris-0.4.0.1-cp39-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 296.1 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
56ea242872e301c13835a647872fbae3653bd434142d0b3f39c32a0f7c4a4a3b
|
|
BLAKE2b-256 checksum How to use checksums |
db6d4bd0c92f0d133ea7c91f81912da0a893dc05862ad45e53a2239c7d4d43ee
|
| 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.4.0.1-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | yeptris-0.4.0.1-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 301.0 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
e7ac4df25e64a4c9fbf9ba47ab8b618873cbbb1216e59c0af003cd2dc806001f
|
|
BLAKE2b-256 checksum How to use checksums |
3309c478d9bf43f0cadd91431ffd1a6e041de2fb6b93afced9e3de790bc8d9fc
|
| 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.4.0.1-cp39-abi3-macosx_11_0_x86_64.whl
| Download URL | yeptris-0.4.0.1-cp39-abi3-macosx_11_0_x86_64.whl |
|---|---|
| Size | 263.5 kB |
| Tags | CPython 3.9 abi3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
02a1cc76c6a3452780a9c9c89a48fd0df58e77c30ec975a70117b70cf9ba2332
|
|
BLAKE2b-256 checksum How to use checksums |
57d6cd980e59e02b86f128fa37a4c07a447bbf43a90dd2fad1606496cc4c6b72
|
| 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.4.0.1-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | yeptris-0.4.0.1-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 252.0 kB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d0c68a84107a4fa971524be03cdebd9e37115fd9e4eef2c8036e4b4d6abd85b4
|
|
BLAKE2b-256 checksum How to use checksums |
4c8ac3000522343ab19bba95f46c57052e8a9bf78ddc559923bfdfcf5e24c064
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.5
|
