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.5.2.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.5.2.1.tar.gz | 25.2 kB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| yeptris-0.5.2.1-py3-none-any.whl | Python 3 | none | any | Details |
| yeptris-0.5.2.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.5.2.1-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| yeptris-0.5.2.1-cp39-abi3-macosx_11_0_x86_64.whl | CPython 3.9 | abi3 | macOS 11.0+ x86-64 | Details |
| yeptris-0.5.2.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.5.2.1.tar.gz
| Download URL | yeptris-0.5.2.1.tar.gz |
|---|---|
| Size | 25.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0c2c5a669d3d27019a76d8ce87803c966f2b9016c472ccb4de1f0137567a42bc
|
|
BLAKE2b-256 checksum How to use checksums |
507ba109e2cd593afe5604bc2f4d8e68368fcf1cff19dab341aeda6347afe4a3
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.
Transparency logRelease files / yeptris-0.5.2.1-py3-none-any.whl
| Download URL | yeptris-0.5.2.1-py3-none-any.whl |
|---|---|
| Size | 18.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2b81893e7221aa690da53e689544296baccdb2f9370a4d760faebdb15d1f771c
|
|
BLAKE2b-256 checksum How to use checksums |
f61ad10f03627418ef001368f388513c741353d909e393af76552cc6ec01d0e4
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.
Transparency logRelease files / yeptris-0.5.2.1-cp39-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | yeptris-0.5.2.1-cp39-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 297.9 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
2525f763e392513b2ef776f3f7dc5eef97a89b6826305c0a9931e0e86c7b5ae1
|
|
BLAKE2b-256 checksum How to use checksums |
be0bc96807d38df0eb12b947316764bc878d40757eef60404f8fe608ab5ce3aa
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.
Transparency logRelease files / yeptris-0.5.2.1-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | yeptris-0.5.2.1-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 303.0 kB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
56702d7784a5659894ab5c30a925370e25bad27c8dc62b82f3f2e885403420c5
|
|
BLAKE2b-256 checksum How to use checksums |
5722786d7b20e76e58635f3563453f7775e4b5d1a3707c8f30da22b26b092ab5
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.
Transparency logRelease files / yeptris-0.5.2.1-cp39-abi3-macosx_11_0_x86_64.whl
| Download URL | yeptris-0.5.2.1-cp39-abi3-macosx_11_0_x86_64.whl |
|---|---|
| Size | 264.6 kB |
| Tags | CPython 3.9 abi3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
a7f3e1de5b4a96eebb60e7de178ddb27a09b9401c9ee22fca7246683284fb5f7
|
|
BLAKE2b-256 checksum How to use checksums |
deb599b9db9f83a76abb03b4e55d265869410c14f787a7ef55f6d15ed5fba4a7
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.
Transparency logRelease files / yeptris-0.5.2.1-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | yeptris-0.5.2.1-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 253.1 kB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
c341329da3c25ee7d1dfc80b52a2b76db5f1937c1f996b664acdef4ecf014fb3
|
|
BLAKE2b-256 checksum How to use checksums |
afeeced1aaf399d3aa1babf701858316bc5b6245c41d83aec30026cf5bd7fde9
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 16, 2026.
Transparency log
