leptris (Python) — lxml-shaped bindings for libleptris
leptris wraps the libleptris
C API (XML 1.0 parsing, XPath 1.0) using cffi in ABI mode, with a
required C accelerator for Element allocation and the hot accessors
(tag, text, attrib, get, indexing, sibling navigation and
plain-path XPath evaluation). Wheels ship it compiled; sdist builds
require a C compiler.
The pinned libleptris version lives in libleptris-version.txt
(lockstep releases); CI builds it from the release tarball.
Platform wheels bundle the compiled engine — pip install leptris works with no extra setup on macOS (x86_64/arm64), Linux
(manylinux + musllinux, x86_64/aarch64) and Windows (amd64/arm64).
Requirements
- Python 3.9+
cffi(installed automatically)- nothing else for wheel installs — the pinned libleptris is
vendored into
leptris/_vendor/by the wheel build (scripts/vendor_libleptris.sh). Wheels carry the compiled library AND its exact source (_vendor/engine/, with rebuild instructions in_vendor/README.md) - source installs (
pip install --no-binary leptris) need a C toolchain + cmake; the sdist bundles the pinned engine source and compiles it at install time — noLEPTRIS_LIB_PATH
Supported runtimes
- CPython 3.9+ (abi3 wheels; one wheel per platform covers every supported CPython, including future 3.x releases)
- Free-threaded CPython (3.13t/3.14t): supported — cp314t wheels
ship for every platform, built with
Py_GIL_DISABLED(version- specific; the accelerator's Fns table is write-once at import). Contract: one document per thread (documents may migrate between threads between calls); the shared SAX recorder is internally serialized - PyPy / GraalPy: unsupported — the accelerator is required (single-mode by design); a pure-cffi fallback would contradict the binding's purpose. Revisit only on real demand.
Wheel platforms
Every release ships a universal wheel per platform (abi3, covering all CPython 3.9+) plus the matching free-threaded cp314t wheel and a source distribution. Each wheel runs the full test suite on its platform as part of the release build.
| Platform | Wheels | Notes |
|---|---|---|
| Linux x86_64 (glibc ≥ 2.17) | abi3 + cp314t | manylinux |
| Linux x86_64 (musl) | abi3 + cp314t | musllinux (Alpine) |
| Linux aarch64 (glibc / musl) | abi3 + cp314t | native runners |
| Linux ppc64le | abi3 | full suite under qemu |
| Linux s390x | abi3 | big-endian; full suite under qemu |
| Linux i686 (glibc + musl) | abi3 | full suite (musl under qemu) |
| Linux armv7l (musl) | abi3 | full suite under qemu |
| macOS x86_64 + arm64 | abi3 + cp314t | universal2; x86_64 slice Rosetta-tested |
| Windows x64 + ARM64 | abi3 + cp314t | suite runs on both architectures |
| Windows x86 (32-bit) | abi3 | first wheel in 1.9.280.0 (engine #1456) |
Every leg is required: a red leg fails the release before publish.
For a development checkout (or to use your own libleptris
build), the loader also accepts a shared library
(libleptris.dylib / .so / .dll) on the loader path, or one
named by LEPTRIS_LIB_PATH (which must name the library
file — the loader dlopens it verbatim; it takes precedence
over the vendored copy):
cmake -B build -S /path/to/leptris -DLEPTRIS_BUILD_SHARED=ON
cmake --build build --target leptris_shared
export LEPTRIS_LIB_PATH=/path/to/leptris/build/src/libleptris.dylib
Quick start
from leptris import fromstring, tostring
root = fromstring("<library><book id='1' lang='en'>Ulysses</book></library>")
root.tag # "library"
root[0].get("id") # "1"
root[0].attrib # {"id": "1", "lang": "en"}
root[0].text # "Ulysses"
root.xpath("count(//book)") # 1.0
[b.text for b in root.findall("book")] # ["Ulysses"]
tostring(root[0], encoding="unicode") # "<book id=\"1\" lang=\"en\">Ulysses</book>"
Documents own the tree; use the context manager or close():
from leptris import parse
with parse("catalog.xml") as doc:
doc.xpath("//book[@lang='en']")
Namespaces, variables, canonical XML and streaming:
root.xpath("//x:item", namespaces={"x": "urn:ex"})
root.xpath("//book[@id=$id]", variables={"id": "2"})
c14n(root, exclusive=True)
from leptris import sax
sax.parse(xml, handler) # one-shot
with sax.StreamingParser(handler) as parser: # push, constant memory
parser.feed(chunk, final=last)
for rec in sax.records(xml): # one-crossing records tape
... # (leptris 1.9.237.1+)
XSLT and XPath version support
leptris.XSLT(stylesheet) compiles once, applies to any Document, and
returns a Document; leptris.XPath(expression) compiles an XPath for
repeated evaluation. Which language constructs work is decided by the
engine — the matrix below is measured against libleptris 1.9.32
(audited through this binding; the upstream gap ledger is
leptris/leptris#685).
| language | status | notes |
|---|---|---|
| XSLT 1.0 | full | libxslt conformance suite 205/205 upstream; EXSLT math/set/str/date included |
| XSLT 2.0 | partial | ✓ for-each-group, analyze-string + regex-group(), xsl:number formats, xsl:assert, xsl:sequence (multi-item), xsl:perform-sort · ✗ xsl:function, tunnel parameters, shadow attributes, xsl:result-document, @separator |
| XSLT 3.0 | increments | ✓ try/catch (with $err:description), accumulator (gated by xsl:mode use-accumulators), iterate + break + on-completion, on-empty, evaluate, grouping, modes, where-populated, on-non-empty, next-match, fork, @start-at, composite keys, tunnel params, copy/@select, xsl:namespace, xsl:document, @default, merge, result-document (writes the href target), character maps · ✗ package, xsl:map, xsl:evaluate with-params, next-iteration chaining |
| XPath 1.0 | full | complete core function library |
| XPath 2.0 | grammar complete | ✓ quantified (some/every), set algebra (union/intersect/except), node comparisons (is, <<, >>), (), ends-with, deep-equal, value comparisons, cast/castable/treat/instance of, function items + HOFs (1.9.73+) · function slices by group (sequences, regex, math:, strings/QNames/URIs, dates, xs: constructors); remaining: format-date/format-time, JSON, map:/array: constructors · format-number works in plain XPath since 1.9.80 |
| XPath 3.1 | lane 0 | ✓ let, simple map !, arrow =>, string concat || — through both XPath() and XSLT · ✗ function items, inline functions, maps, arrays, string constructors |
| DTD | validation | leptris.DTD(text) / .from_file(path) / .from_document(doc) (the DOCTYPE internal subset, doc-owned) — compile once, .validate(doc) → bool with .error_log (message/element/line/column); .parse_external_subset(text) merges external declarations (first-decl-wins), .set_pe_loader(fn) resolves external parameter entities with application-owned I/O — libleptris 1.9.202+ |
| XSD (W3C XML Schema) | tier 1 | leptris.XSD(text) — schema compilation + lexical validation: valid_builtin("xs:integer", "42") and valid(type_name, lexical) over user simpleTypes with restriction facets — libleptris 1.9.319+; instance validation xsd.validate(doc) → bool with enumerated error_log; XSD.from_file(path) resolves relative xs:include/xs:import schemaLocations (#1075 complete — content models, instance validation, identity constraints) — libleptris 1.9.321+ |
| RELAX NG | core subset | leptris.RelaxNG(schema) / .from_file(path) — compile once, .validate(doc) → bool with Jing-shaped .error_log; element/attribute/text/data/value/choice/group/interleave/repeats/ref — libleptris 1.9.115+ (#878) |
| XML diff | native | leptris.diff(a, b[, ignore_ws_text]) — digest-pruned ordered edit script (iterate DiffOp(type, path, name, before, after); serialize() line-per-op) — libleptris 1.9.144+ |
| XQuery | 1.0 core + 3.x increments | leptris.XQuery(query) — FLWOR (for/let/where/order by/return/group by, positional at, tumbling/sliding windows), prolog (declare variable/namespace/function local:* incl. external variables with QT3-style select bindings via variables=),, constructors, doc()/collection(), try/catch, typeswitch — libleptris 1.9.68+; 3.1 remainder (maps/arrays, modules) tracked in #684 |
XQuery 1.0 core is a first-class API since libleptris 1.9.64:
from leptris import Document, XQuery
with Document.parse("<r><item v='1'>alpha</item><item v='5'>beta</item></r>") as doc:
XQuery("for $i in //item where $i/@v > 1 return string($i)")(doc) # ['beta']
XQuery("declare variable $n := 3; <out>{$n * 2}</out>")(doc) # [<Element 'out'>] — real nodes (1.9.314+); tostring() for markup
XQuery("declare function local:dbl($x) { $x * 2 }; local:dbl(4)")(doc) # 8.0
Schema-descriptor materialization (Plan, libleptris 1.9.162+)
Compile a descriptor once, materialize whole documents in one native pass — the tree-shaped ABI lutaml-model hosts consume (leptris/leptris#1039):
from leptris import Document, Plan
catalog = Plan({
"element_name": "catalog",
"children": [
{"name": "item", "kind": "collection", "plan": {
"element_name": "item",
"attributes": {"id": {}, "price": {}},
"children": [{"name": "title"}],
}},
{"name": "note", "kind": "raw"},
],
})
with Document.parse(xml) as doc:
data = catalog(doc) # {"attributes": {...}, "children": {...}}
Row kinds: scalar, collection (list), nested (element plan),
raw (serialized subtree), content (mixed-content text runs, name
may be ""), callback (PlanCallback(value, position, type_tag)
— the escape hatch for host-side procs). Results are shape-stable
(absent rows yield None / []); namespace forms via
ns={"form": "none"|"exact"|"any", "uri": ...}, flags via
{"mixed_content", "ordered", "cdata", "ns_lenient"}.
The default surface is the full XPath 3.1 grammar. To pin the
strict XPath 1.0 surface (3.x-only syntax raises XPathError),
pass version="1.0" — on Document.xpath, Element.xpath, and
the compiled XPath class (XPath(expr, version="1.0")):
root.xpath("count(//book)", version="1.0") # works — 1.0 grammar
root.xpath("//book ! @id", version="1.0") # XPathError: 3.x syntax
XPath("//book[1]/@id", version="1.0")(root) # compiled + strict
XPath 3.1 composition and XSLT 3.0 instructions flow through the existing API with zero binding change:
from leptris import Document, XPath, XSLT, tostring
with Document.parse("<r><item v='1'>alpha</item><item v='5'>beta</item></r>") as doc:
doc.getroot().xpath("let $n := //item[2] return $n/@v") # ['5']
doc.getroot().xpath("(//item ! string(.)) => count()") # 2.0
style = XSLT("""<xsl:stylesheet version="3.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:mode use-accumulators="depth"/>
<xsl:accumulator name="depth" initial-value="0">
<xsl:accumulator-rule match="*" phase="start" select="$value + 1"/>
<xsl:accumulator-rule match="*" phase="end" select="$value - 1"/>
</xsl:accumulator>
<xsl:template match="/"><o>
<xsl:iterate select="//item">
<i d="{accumulator-before('depth')}"/>
</xsl:iterate>
</o></xsl:template>
</xsl:stylesheet>""")
print(tostring(style(doc), encoding="unicode"))
# <o><i d="2"/><i d="2"/></o> # items sit at depth 2 (r → item)
Unsupported constructs fail at XSLT() compile time or at evaluation
with LeptrisError — except two instructions that still produce
empty output instead of an error (xsl:map/xsl:map-entry, and
xsl:value-of/@separator is ignored); tracked in the
#685/#690 ledgers above.
HTML parsing
leptris.html (libleptris 1.9.75+) — tolerant HTML in the shape of
lxml's etree.HTMLParser: implied end tags, void elements,
case-insensitive names, unquoted attributes, the named-entity
table, and a synthesized <html>/<head>/<body> wrapper:
from leptris import html
r = html.fromstring("<p>hello <b>world") # <html><head/><body><p>hello <b>world</b></p></body></html>
with html.document("<td>c") as doc:
doc.xpath("count(//td)") # 1.0
Since libleptris 1.9.76 the output is byte-exact with lxml's
etree.HTMLParser (minimized attributes are empty strings; no
empty <head/> is emitted) — leptris/leptris#813. The one
deliberate html4 divergence: a leading script/style run
stays in body (the fragment shape), where lxml's libxml2 lifts
it to head.
Two modes (libleptris 1.9.104+): the default html4 keeps this
compatibility shape; mode="whatwg" selects the WHATWG-conformant
engine — with libleptris 1.9.196 the WHATWG conformance corpus is
at zero divergences (leptris/leptris#659 complete): tree
construction, foster parenting, adoption agency, in-select/table
scope, and the foreign-content rules all match the specification.
leptris fully provides HTML.
Building HTML works like building XML, on an HTML-mode document —
serialization emits void elements without closing tags and keeps
<br>-style names un-XHTML-ed (libleptris 1.9.225+):
from leptris import html
import io
doc = html.create()
p = doc.create_element("p", {"class": "intro"})
doc.set_root(p)
p.text = "hello"
buf = io.BytesIO(); doc.save_html(buf) # <p class="intro">hello</p>
tostring(node, method="html") forces HTML output for any tree;
HTML-parsed and html.create() documents serialize as HTML by
default.
Migrating from lxml
| lxml | leptris | Notes |
|---|---|---|
etree.fromstring / etree.XML |
fromstring / XML |
|
etree.parse |
parse |
paths and file-likes; no URLs |
etree.tostring(elem, …) |
tostring(elem, …) |
bytes by default, encoding="unicode" for str |
elem.tag / .text / .tail |
same | tag uses {uri}local Clark notation; CDATA merges into text (lxml's default parser behavior) |
elem.attrib / .get() / .keys() / .items() |
same | attrib is a read-only Mapping |
elem.getparent/getnext/getprevious |
same | |
elem[i], len(elem), iteration, slices |
same | indexing is child indexing, never attribute lookup |
elem.iter() / .iterdescendants() / .itertext() |
same | elements only (ElementTree semantics); lxml's iter() also yields comments/PIs |
elem.find/findall/findtext |
same | accepts full XPath 1.0 — a superset of ElementPath — including {uri}local names |
elem.xpath(expr, namespaces=…) |
same | plus variables={…} (leptris extension) |
etree.c14n / etree.XInclude |
c14n(…) / doc.process_xinclude() |
|
etree.XMLSyntaxError |
ParseError |
XPath failures raise XPathError; XSLT raises XSLTError, XQuery XQueryError — all subclass LeptrisError |
etree.Element/SubElement/append/set |
create path | Document.create() + create_element(name) + set_root() (returns the installed element; foreign parentless elements adopt by copy, 1.9.298+), Element.create_child(name)/append(el)/set(name, value) + the .text setter — libleptris 1.9.216+; remove via Document.remove_* (doctype/child) |
| document-level comments / PIs | doc.toplevel_comments() / doc.toplevel_pis() |
prolog then epilog; requires libleptris 1.9.3+ |
etree.iterparse |
leptris.iterparse(source, full_document=False) |
bounded by the largest subtree; yields ("end", element); elements borrowed until the next yield; tags resolve namespaces (Clark notation, libleptris 1.9.4+). Truncated or malformed input raises ParseError (both modes, libleptris 1.9.15+). full_document=True yields every element in completion order. Perf opt-outs: skip_dup_detection=True / skip_source_positions=True (libleptris 1.9.284+, ~48% faster on diagnostics-free streams) |
| smart strings | plain str |
XPath string/attribute results |
elem.nsmap |
absent | use elem.namespace / elem.prefix and xpath(namespaces=…) |
etree.XPath compiled objects |
leptris.XPath(expression) |
compile once, evaluate many; contexts, namespaces, and variables supported |
etree.XSLT |
leptris.XSLT(stylesheet) |
compile once, apply to any Document — see the version support matrix above; apply-time top-level params: transform(doc, params={"n": "//v"}) (XPath-expression values, libleptris 1.9.287+) or string_params for the serialized result |
elem.sourceline |
same | requires libleptris 1.3.0+ |
| undeclared XPath prefix | raises in lxml | evaluates to an empty nodeset here |
| ATTLIST default attributes | applied by lxml's default parser | excluded by default (ElementTree-like; XML 1.0 §5 permits either) — Document.parse(xml, attribute_defaults=True) opts in |
| declared non-UTF-8 bytes (UTF-16, latin-1, …) | auto-detected | auto-detected — declared encodings route through the converter, others retry on failure (libleptris 1.9.15+) |
parser options (remove_blank_text, …) |
etree.XMLParser(remove_blank_text=True) |
Document.parse(xml, remove_blank_text=True) — ~35% faster on pretty-printed input; also attribute_defaults=True, recover=True, and the perf opt-outs skip_dup_detection=True / skip_source_positions=True (1.9.273+, ~13% faster on diagnostics-free workloads); the streaming twins on iterparse/sax.parse/StreamingParser (1.9.284+, ~48% on streams) |
| bulk attribute read | — | elem.attribute_pairs() — all attributes as (name, value) pairs in one C pass (1.9.216+) |
| typed attribute read | — | elem.get_int/get_float/get_bool(name, default) — conversion engine-side, one crossing (1.9.280.1+); strict: unparseable or missing -> default |
| subtree walk | elem.iter() |
elem.visit_entering(fn) — one callback per node entered, document order, no re-visit after the subtree (1.9.232+) |
| catch-all child rows | — | plan child rows take {"kind": "wildcard"} — the unbound remainder as RAW subtrees (or walked via a nested "plan"); Plan.serialize(doc) serializes a walk back to XML with ns_prefix declarations (1.9.312+) |
| content digest | — | elem.digest([drop_whitespace][, attr_order]) — Merkle hash of the subtree; stable across processes (attr_order: 1.9.208+) |
Layout
leptris/_ffi.py— cdef mirror of the public headers + loader (the only place libleptris is declared)leptris/_engine.py— the compile-once lifecycle base shared by the compiled language objects (XSLT,XQuery, futureRelaxNG)leptris/_results.py— the result model: engine results to Python values (nodeset wrapping, scalar conversion), shared by every evaluation surfaceleptris/_leptrisaccel.c— the C accelerator (abi3): allocates Elements and runs the hot accessors, subtree iteration, the parse and serialization seams, and the per-document element registry; bound to libleptris by the positional protocol inelement.pyleptris/element.py,document.py,node.py,xpath.py— the Python surface: queries, walks, documents;node.pyexposes the full DOM (comments, CDATA, PIs) beneath the ElementTree shapeleptris/api.py—fromstring/parse/tostring/c14n/iterparseleptris/sax.py— SAX one-shot and streamingtests/— pytest suite (pytestwithLEPTRIS_LIB_PATHset)benchmarks/— matrix vs lxml/ElementTree/minidom (pip install .[bench], thenpython -m benchmarks.matrix)
Memory model
The Document owns the whole tree and its pool. Accessor strings
are copied into Python str at the boundary, so nothing depends on
document lifetime after a call returns. Elements keep a reference to
their Document, so the pool cannot be freed while any wrapper is
alive. Prefer explicit close() / the context manager; __del__ is
a refcounting safety net, not a contract. Using an element after its
document is closed raises LeptrisError.
Versioning
libleptris-version.txt pins the library release the binding is
built and tested against. Since 1.9.76.0 the package version is
{c-full-semver}.{patch} — the pinned libleptris version plus
a binding-local patch counter: lib 1.9.76 → 1.9.76.0, then
1.9.76.1 for binding-only fixes against the same pin, resetting
the patch whenever the pin moves. (1.2.0–1.27.1 were the interim
own-semver line.) pyproject.toml and leptris/__init__.py must
agree at release time.
Publishing
Releases publish to PyPI via .github/workflows/release.yml, using
PyPI trusted publishing (no stored credentials). The workflow
runs on manual dispatch (ships the version in pyproject.toml) and
is called by the libleptris release flow (publish: true), so every
libleptris release ships the wheel.
Local development
python3 -m venv .venv
./.venv/bin/pip install --upgrade build pytest cffi
./.venv/bin/pip install -e .[test,bench]
LEPTRIS_LIB_PATH=/path/to/libleptris.dylib ./.venv/bin/python -m pytest tests/ -q
Release files for leptris 1.9.331.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| leptris-1.9.331.0.tar.gz | 4.1 MB | Details |
Built distributions (wheels)
Total release size: 55.7 MB
Release files / leptris-1.9.331.0.tar.gz
| Download URL | leptris-1.9.331.0.tar.gz |
|---|---|
| Size | 4.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4eabc7bc8ab2417f0cabf769925e36cd8c34b6afb0d4270664aab816d3fc9e0
|
|
BLAKE2b-256 checksum How to use checksums |
2a5535db3eb61dfc13f12f142eb786a573d63e14bdcebf3bf79b3a6d4a09ab42
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp314-cp314t-win_arm64.whl
| Download URL | leptris-1.9.331.0-cp314-cp314t-win_arm64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows ARM64 |
|
SHA-256 checksum How to use checksums |
ec6ee94fc253550a8e227b0b1c45029e2ebedbcfaacb5fc668746cfdb4d48f53
|
|
BLAKE2b-256 checksum How to use checksums |
d70b2655f75f17c6c56db0f5cfa0a741adaf5ded55d356cce2cfb9971e11c4c5
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp314-cp314t-win_amd64.whl
| Download URL | leptris-1.9.331.0-cp314-cp314t-win_amd64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows x86-64 |
|
SHA-256 checksum How to use checksums |
c91c0987101c989a27f84f5867e355bbc64ffdbdd929afc330a95d6bf12b8144
|
|
BLAKE2b-256 checksum How to use checksums |
772209c0006041627e4261863d87742d442941b8823d2815f4142a9a4dab751e
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp314-cp314t-musllinux_1_2_x86_64.whl
| Download URL | leptris-1.9.331.0-cp314-cp314t-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
63fcfcfb4fdccc623dcb22ad2c2fe0cf51bb74713826a041cf2e00a96c6f4479
|
|
BLAKE2b-256 checksum How to use checksums |
35cd1d973f381b716dfeb489bb575aba0f9b9fd205d1fcbc90894b70cc6d696a
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp314-cp314t-musllinux_1_2_aarch64.whl
| Download URL | leptris-1.9.331.0-cp314-cp314t-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
59a14dcfe873ecd727514925a6f0c775fd03d51b523541d08de7656eb4af18c5
|
|
BLAKE2b-256 checksum How to use checksums |
1e3dd9b642ac3ed4b9ba0a4a2dc2691750f15263eb1a21cfbc5c986d07dc6ce0
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | leptris-1.9.331.0-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
b002a6cc5a539547f6ea71f8e6683260de779c0518a2dbf6e2861f98acd1deeb
|
|
BLAKE2b-256 checksum How to use checksums |
8a78d28d4fb29c21d3df3f12590e5b6759d0f4d0c3931afef55157e2c9864c8c
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | leptris-1.9.331.0-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
12008873044bac1b52fa404a403a1da605f5137cb443c8c1bad4784d396c4887
|
|
BLAKE2b-256 checksum How to use checksums |
772f12237f85f3db28cb7aa455da6111b3e920d58230dfc6d8c5bb66b871956e
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp314-cp314t-macosx_11_0_arm64.whl
| Download URL | leptris-1.9.331.0-cp314-cp314t-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6740ef29427e597f11e73e3e8d1c9c93c997c1d0b16669386a9ec413e50c3e2c
|
|
BLAKE2b-256 checksum How to use checksums |
94285253af3a64c0ba7369ede4c0a276d3dbfb141a82c4c55e1945387bad86aa
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp314-cp314t-macosx_10_15_x86_64.whl
| Download URL | leptris-1.9.331.0-cp314-cp314t-macosx_10_15_x86_64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
5c455cd775ceb7c8a3a3fa906ad6d25fcd78e5174f12000da991c14dcd9b80de
|
|
BLAKE2b-256 checksum How to use checksums |
38878e4a3ed2e455fd9b2a55bb3cb6b94c18129f56a44c86b54a9f576f43545e
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-win_arm64.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-win_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.9 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
28a2fd0acd80337c71b5dc374cca107b045f1d4b575af851bd679b396657579d
|
|
BLAKE2b-256 checksum How to use checksums |
edb6c675a41372ad82da018fede0d3f317c24182ef1d4dc5746b584e235d3b42
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-win_amd64.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
fe87febf4d226d92a61c1effc7ef7c1298f28e8951c64d81f840150a46aec7ff
|
|
BLAKE2b-256 checksum How to use checksums |
83aba6e50db7190c4374ff5857069ff159a30fc6077c766ee91e6489ebcce892
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-win32.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-win32.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.9 Windows x86-32 abi3 |
|
SHA-256 checksum How to use checksums |
9355bdc19eaf67590ea946e2262e8972f9d297f3a92f86f6768de11c19f6e85c
|
|
BLAKE2b-256 checksum How to use checksums |
d37644e6cdee524dac42a4c92412157d014fd66542b9d5210402639f7b73f761
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-musllinux_1_2_x86_64.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.9 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
20df880374edd923fd8d9681c564fb5ed8391a3e00bea37b0eba4bd8728d1dca
|
|
BLAKE2b-256 checksum How to use checksums |
b10ed0c0e495bd76c851195cc2bdd4d3ae6cddd50a25b4bfb492a39097b4cb5c
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-musllinux_1_2_i686.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-musllinux_1_2_i686.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.9 Linux musl 1.2+ x86-32 abi3 |
|
SHA-256 checksum How to use checksums |
54aee733437c4e507724a206d709c2a82d8d1ce13c276b17b893cfa439dcf313
|
|
BLAKE2b-256 checksum How to use checksums |
a5aaae6ec8df7b63f8b94bdab4217b33cf81fd8be951d050b22cbdfb5b7f9c78
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-musllinux_1_2_armv7l.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-musllinux_1_2_armv7l.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.9 Linux musl 1.2+ ARMv7l abi3 |
|
SHA-256 checksum How to use checksums |
bb8dfed8fae85aad2f6a3839f45e994535ea55f0464a914f8722a2b7c68da825
|
|
BLAKE2b-256 checksum How to use checksums |
7c4a715ba7b7138a410e0a6f7691c930c65783f56c3d11c6a5b7bf48b555a414
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-musllinux_1_2_aarch64.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.9 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
77da1d203bc7bfdeffd52089d299d310eae8192cf94182702a1a0ef770a25931
|
|
BLAKE2b-256 checksum How to use checksums |
7abb9dfd6e623d945eb03633fd6d92ba71b4c4e9981adcd6739585ee973bc571
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
dd2d79712d677a1c3f248d3e8ddc7a683addae208f4f6b3ca91cc873200a86a6
|
|
BLAKE2b-256 checksum How to use checksums |
7329ff77d5014c9993472b2f161b4400d0a49c1ab6b63f07b5c1723c09d8efdf
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-manylinux2014_s390x.manylinux_2_17_s390x.manylinux_2_28_s390x.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ IBM System/390x Linux glibc 2.28+ IBM System/390x abi3 |
|
SHA-256 checksum How to use checksums |
1af6e0634612cd3c9bb0cae584ed6d31beebdf49b331819466dcdef3645f70b2
|
|
BLAKE2b-256 checksum How to use checksums |
f109f1afb26d4a2b30c62d7a53dfefa9b7ef89d442e37f9e211491d5587daa4b
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-manylinux2014_ppc64le.manylinux_2_17_ppc64le.manylinux_2_28_ppc64le.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-manylinux2014_ppc64le.manylinux_2_17_ppc64le.manylinux_2_28_ppc64le.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ PowerPC 64-le Linux glibc 2.28+ PowerPC 64-le abi3 |
|
SHA-256 checksum How to use checksums |
13d664777a9bb2796023a9cfc8c42ac7c4ecbaf3668105f41dbf1c32f4bcc460
|
|
BLAKE2b-256 checksum How to use checksums |
f752ed41704e840b4bdd9b16a09c1995e2971c307cb8ad492973c8db408b0a47
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
3500a1529d3a36578cffff402dc4630f2f85b36ee7f4b3777ca664c7832de85a
|
|
BLAKE2b-256 checksum How to use checksums |
c4c4af5c911d0b1353f1243dee7a38a4297fc8805f2f8736da3332dedfdd8b78
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-manylinux2010_i686.manylinux_2_12_i686.manylinux_2_28_i686.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-manylinux2010_i686.manylinux_2_12_i686.manylinux_2_28_i686.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.9 Linux glibc 2.12+ x86-32 Linux glibc 2.28+ x86-32 abi3 |
|
SHA-256 checksum How to use checksums |
57a5ce2456d7516036e48386ab26cb526766954e29526acc20e301d24e30dd92
|
|
BLAKE2b-256 checksum How to use checksums |
9e084bb1c1fbffcc3c40bf5b3544a5604d6a1a3aa2deef1409545a017bd89c1a
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
e5af1b8bbbcd8182462f2a768e3a6c52f77244630c9528e8892da47721e36e1b
|
|
BLAKE2b-256 checksum How to use checksums |
e9eb326242bbd6af05ab6df4866ce04e204d851f20b9b58984fbff9cca9bff3e
|
| 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 Oct 9, 2026.
Transparency logRelease files / leptris-1.9.331.0-cp39-abi3-macosx_10_9_x86_64.whl
| Download URL | leptris-1.9.331.0-cp39-abi3-macosx_10_9_x86_64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.9 abi3 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
519d9e748db6eca3f321e1d5c68a2b0f8a3e8a11641716eb38012d54c9ef68db
|
|
BLAKE2b-256 checksum How to use checksums |
482b3f1542c374070c7941327f33b72cf9dacad99ac5342637dd7e3305b49a76
|
| 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 Oct 9, 2026.
Transparency log
