LibLathe 
LibLathe is an opensource standalone python library for generating turning paths and gcode for use with cnc lathes.
| ⚠️ WARNING: LibLathe is currently experimental / Proof of concept and only suitable for testing. |
Installation
Installing liblathe from PYPI
pip install liblathe
Local install for testing
pip install .
⚠️ Some systems require that packages are system installed. Liblathe can be installed for development purposes. Note: This may break your system
pip install . --break-system-packages
pip uninstall liblathe --break-system-packages
Build
Liblathe is a python library with a C++ core. Liblathe core can be compiled and tested inplace using the following steps:
Native C++ types live in the liblathe namespace, for example liblathe::Point.
Python module and class names are unchanged. Rebuild all five native extensions
together when updating the native headers.
cd Liblathe
cmake .
make
Local testing
python3 ./examples/defeature_example.py
Tests
After building, run the Python suite with pytest --ignore=extern, as used by
the test workflows. These tests exercise the compiled C++ core through Python.
The native memory driver is an optional diagnostic for investigating C++ memory issues, not a required test or CI step. Its header contains the manual build and sanitizer instructions.
Design
Part profiles are lines and arcs in X (radius) and Z (axis). LibLathe plans cuts in two geometry steps:
- Defeature: the tool is moved along the part and only the area it can actually reach is kept, removing features that can't be turned, such as undercuts.
- Offset: a signed distance field (SDF) gives the distance from any point to the profile. A quadtree samples it, refining only near the target distance. Points at that distance are collected, ordered and simplified with the Ramer-Douglas-Peucker (RDP) algorithm into the offset path.
The operations (face, rough, profile and part-off) combine these steps into toolpaths and gcode. The geometry core is C++ exposed to Python with pybind11.
Defeature retains the complete line/arc insert footprint and checks containment as well as edge crossings. Returned points are tool origins, not contact points. Connecting moves and simplified chords must pass an adaptive full-footprint sweep check against the original part. Unsafe direct connectors use a verified axis-aligned route; geometry that cannot be certified within coordinate precision or the subdivision limit raises an error instead of returning an unchecked move. This checks the defeature envelope only, not subsequent offsets, operation paths, or stock clearance on entry and retract moves.
G-code entry and retract routing uses the complete rotated insert bounds to keep
rapid moves outside the original stock envelope. The clearance parameter must
be finite and non-negative; routing applies a minimum clearance of 0.01 model
units. Approaches and escapes use feed moves at hfeed, so these moves may remove
stock. Profile and roughing operations certify the added feeds against the
original part with SegmentGroup.validateToolSweep; an uncertifiable approach
or escape raises an error instead of publishing partial commands for that group.
Facing and parting use the same stock-clear rapid routing but may intentionally
cut the original part region. Rebuild the native extensions for the new sweep
validation binding before using the updated Python routing code.
This conservative routing does not track previously cleared stock. It checks the first rapid destination, not travel from an unknown initial machine position, and does not certify holders, fixtures, all original cutting moves, or machining safety. Reference-equivalent final stock remains a separate validation requirement.
SegmentGroup.getRadialContactPoint() derives a cutting-edge datum from the
native outline, including arc extrema and the axial midpoint of a flat innermost
edge. Roughing uses it to express physical stock limits in tool-origin coordinates
and anchors its pass grid to the stock, rather than a sampled offset endpoint.
Profile uses the same datum for its lead-in plane. These changes require rebuilt
native bindings; they do not establish reference-equivalent Profile final stock.
The SDF uses the profile closed back to X = 0: sign and distance include the same boundary. Artificial closing edges do not generate offset candidates; faces explicitly included in the profile remain eligible. The existing start-Z clip is retained. In LibLathe's plotted view, Z is horizontal and X increases downward from the centreline.
Offset extraction retains nearest-neighbour ordering when it passes the contour certificate. If that ordering fails, the same candidate points are reordered along the original profile, including corner arcs, and checked again against the unchanged 0.05 model-unit accuracy limit. Uncertifiable or collapsed contours still raise an error; chord failures report their endpoints and midpoint error.
See ARCHITECTURE.md for the trade-offs and alternative approaches.
Spindle Side
Tool.side requires a ToolSide enumeration member from
liblathe.tool.tool: ToolSide.NEAR (default, positive X) or
ToolSide.FAR (negative X). Strings are rejected. This development API
requires an updated build; an older package reporting 0.0.8 may lack the enum.
Supply the tool outline in its actual physical orientation. For Far, supply
negative-X part and stock geometry too; positive-X stock or part inputs are
rejected. BaseOP.getGCode() plans on reflected copies of all three inputs,
then returns physical signed commands, tool_paths and clearing_paths. Reflection reverses
segment bulges, G2/G3 and I offsets, including rapid and retract X positions.
Original inputs are not modified, and near-side behavior is unchanged.
The returned Far-side commands remain negative X. X positions and I arc-centre offsets are negated; G2/G3 are swapped. Z, K and feed values are unchanged. Side does not choose spindle speed, M3/M4, tool handedness or controller G41/G42. The machine integration must match this signed-X contract to its controller.
This selects the spindle side, not inside/outside machining. Internal boring requires separate operation support. Full operation-path safety and native-tool precision sensitivity remain unresolved; signed-side output is experimental and is not machining approval.
Native Tool Geometry
Tool.set_tool_from_segments() accepts the actual XZ insert outline, including
rounded nose arcs. Outline coordinates are relative to the selected tool origin;
returned paths position that origin, not a separately calculated contact point.
The caller supplies the physical pose and datum. LibLathe does not have a
Compensation selector or automatically recenter an imported insert.
Leave tool_rotation at zero for geometry that is already rotated. Its optional
rotation acts around the supplied origin; it is not the add-on's absolute insert
angle or a controller Q orientation. Changing side does not rotate the stored
insert or select its active nose.
See the tooling manual for the API, coordinate conventions and side-planning details.
Examples
Facing:
Roughing:
Profiling:
Parting:
Links
1 maintainer
Metadata
1 maintainer
Release files for liblathe 0.2.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 | Provenance | Actions |
|---|---|---|---|---|
| liblathe-0.2.0.tar.gz | 50.6 kB | With provenance | Details for liblathe-0.2.0.tar.gz |
Built distributions (wheels)
Total release size: 26.0 MB
Release files / liblathe-0.2.0.tar.gz
| Download URL | liblathe-0.2.0.tar.gz |
|---|---|
| Size | 50.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
be8b117eca0701adae8d5eb4de5c14f91e233a964f440a4acdf7f9c8d66c68e5
|
|
BLAKE2b-256 checksum How to use checksums |
03496a87e0824ecbad28224cebb439d3bacfd74a8ae648c728b22227d5e39fc8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-pp312-pypy312_pp80-win_amd64.whl
| Download URL | liblathe-0.2.0-pp312-pypy312_pp80-win_amd64.whl |
|---|---|
| Size | 830.2 kB |
| Tags | PyPy 3.12 PyPy 3.12 8.0 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
2f8a812c16ba96cc76cb6c03726538a12b5b54c429621ab57cb5570e35923aed
|
|
BLAKE2b-256 checksum How to use checksums |
a49d4d22b0598828dea6b7444fa50bf860732c9c1a6a6542c30a7dd5d5a4aad9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-pp312-pypy312_pp80-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
| Download URL | liblathe-0.2.0-pp312-pypy312_pp80-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 694.5 kB |
| Tags | Linux glibc 2.24+ x86-64 Linux glibc 2.28+ x86-64 PyPy 3.12 PyPy 3.12 8.0 |
|
SHA-256 checksum How to use checksums |
4207f8c4b1e35a2a874f3cd059f473d7ca5fe088a8a3f8586d3159342a3b719d
|
|
BLAKE2b-256 checksum How to use checksums |
9a50d444c77e46ee95c46d84751f0a4ff94c901130d3931ec3816b31918b5246
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-pp311-pypy311_pp80-win_amd64.whl
| Download URL | liblathe-0.2.0-pp311-pypy311_pp80-win_amd64.whl |
|---|---|
| Size | 829.1 kB |
| Tags | PyPy 3.11 PyPy 3.11 8.0 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f58a539538a4587bf677511c08cbb723e3826ace4a3fbe05578987d989592a6e
|
|
BLAKE2b-256 checksum How to use checksums |
6b12bead2ba5da5ec8faf2983901629874071e0c8f257dfc2b7c0895bdb072c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-pp311-pypy311_pp80-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
| Download URL | liblathe-0.2.0-pp311-pypy311_pp80-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 692.9 kB |
| Tags | Linux glibc 2.24+ x86-64 Linux glibc 2.28+ x86-64 PyPy 3.11 PyPy 3.11 8.0 |
|
SHA-256 checksum How to use checksums |
a9b6c357c5c4298c66169b0c8fee57c4ffa888ab40a9e59931ccabe6cea5a10c
|
|
BLAKE2b-256 checksum How to use checksums |
a183fc71ef4f56445d985a4052c5667eb7be650d9d5b9bf886c588e15bbdfc0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp314-cp314-win_amd64.whl
| Download URL | liblathe-0.2.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 791.7 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
81132a1f17001db9088f5feb33b9abed80ad0782b07992853d746cc951143c97
|
|
BLAKE2b-256 checksum How to use checksums |
3cbdf19e1029cdbb69a65a71da323d08ac7243320704fa3a32e724e094953f98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp314-cp314-musllinux_1_2_x86_64.whl
| Download URL | liblathe-0.2.0-cp314-cp314-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.14 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
724e3ab1fe81dbfce7ca80e98b373e7fc61cb764e9ab4d333cb28d856c415ccd
|
|
BLAKE2b-256 checksum How to use checksums |
0ffe7c2c18bc653f6cd8418986f9f4864664200e2991d058483b5ba81d399a20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | liblathe-0.2.0-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 835.2 kB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
119d9961cde6fc8edd6ecee678dd020241266cca7858fc76c6640713f090cdc8
|
|
BLAKE2b-256 checksum How to use checksums |
e438cfd1671e8f6cd59d08e132bb5b543394888c2ea24c22313f098d28782f33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | liblathe-0.2.0-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 592.4 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a242e442b5f6dea1103c3dd04f9772531a0d451ce9d468f7462e3c07ccf9939b
|
|
BLAKE2b-256 checksum How to use checksums |
7baad0585725128006b53ea19d98db217f0bd16a2df121471fe607a4b956cdd6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | liblathe-0.2.0-cp314-cp314-macosx_10_15_x86_64.whl |
|---|---|
| Size | 628.1 kB |
| Tags | CPython 3.14 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
098d8abf0e05ccf6059fab576f5f8e1801af66eb1743f1c1bbe9d418805fb1f0
|
|
BLAKE2b-256 checksum How to use checksums |
955b94c5fba48c2783f8120ade10c1588d768573067382195347161e782344d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp313-cp313-win_amd64.whl
| Download URL | liblathe-0.2.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 769.6 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f488432331e3eacb3c5f288b290eacf8d4532813f091992714ba565b53d0d1c0
|
|
BLAKE2b-256 checksum How to use checksums |
00610cd7f174b665e407cbe54131279d69fb2e5780508fe72700f95b572dc048
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | liblathe-0.2.0-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
1b6ac5f06207746f060ce194d2fc6b0a3321452350b92cf4400a32fa84677d78
|
|
BLAKE2b-256 checksum How to use checksums |
f7db71d142ca10eccf39844aa6faef0ca6f4686d3b579b8eb4f71856f97d45e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | liblathe-0.2.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 834.9 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
4182ada7e7deaedfce8b7cabc84337512eb7438ff7f07603dd9f090a94e64a0a
|
|
BLAKE2b-256 checksum How to use checksums |
3be67cc228095c9755cf0bd7188f09da003a819a2183fa04a450fc6d90e98c79
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | liblathe-0.2.0-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 591.1 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
6689ff87de7a13261604b0f1177a80b1b591aeff342b3c7087aa23050d31d9d9
|
|
BLAKE2b-256 checksum How to use checksums |
f99aecf54644875fcbc848959044667832a15a728a14b341f99512c5634b54f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | liblathe-0.2.0-cp313-cp313-macosx_10_13_x86_64.whl |
|---|---|
| Size | 627.8 kB |
| Tags | CPython 3.13 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
719021bb25d5b4d31d09e3e7714794ec390264fc4615544ed95c43c92bf6f783
|
|
BLAKE2b-256 checksum How to use checksums |
7cfcd3f6973d1ab56d139c42e22dbea4f7c2e571bd5f949860db3fa0b7a78171
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp312-cp312-win_amd64.whl
| Download URL | liblathe-0.2.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 769.4 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
42ee40e4d52f0d540e0cd1ae859f01f555bdf2bc2887c984c8958e64e4fcd618
|
|
BLAKE2b-256 checksum How to use checksums |
d5666120fc80819ca760bd63b861bc18e8ee6a16912620aa89579036efec33c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | liblathe-0.2.0-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
a474b1e0cb9a85cb4f87deb4dd9ec043918a989e65bb4205feb9ac318f679993
|
|
BLAKE2b-256 checksum How to use checksums |
89ec37c4619205d911a002a0c2985ffabe16c0e454baa268c3eb585c71328468
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | liblathe-0.2.0-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 834.5 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
ec163249d2a70243cfdf029b2e013656b0b27bb89d2cbd43a682233f216cc458
|
|
BLAKE2b-256 checksum How to use checksums |
49956808c64ab3232f05fec28d38621efd5d046d857d62967da6856f9a1ea54d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | liblathe-0.2.0-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 591.0 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
8304ae9375e383b1b085395523e307a4a63c3c7c9862e4eff6938d7c1aadbfc5
|
|
BLAKE2b-256 checksum How to use checksums |
a4d78eb8515e025b33ace9086ce59626a4831aae96b5b364d06ff29f9d7a6754
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | liblathe-0.2.0-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 627.3 kB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
3dfeea0681a822ff3be7e0fdb264751677e8f43392bbdfbc527bc3602162b510
|
|
BLAKE2b-256 checksum How to use checksums |
dca42e1d81b51aaf66af799f5c5b78e1d3cc9bd85233ddd6046319d57275158f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp311-cp311-win_amd64.whl
| Download URL | liblathe-0.2.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 760.8 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
aabf3910eda3853889e21793e946f470bbe5d84fb2f80a9bc7b369d667c21c98
|
|
BLAKE2b-256 checksum How to use checksums |
cd0966381c9d735a258d692dc192c884bed8b392cc5ddfb7d21e0b759e09f71c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | liblathe-0.2.0-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
a749bf2d3cf16d39973ac9ae35464d1a06dcafb7f869c9be072a23b86937bbb9
|
|
BLAKE2b-256 checksum How to use checksums |
e4dac6a0d8e977d24ba73ea6206b9a54914e966d6d87df3f5c09379a965f51ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | liblathe-0.2.0-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 833.4 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
34a94f61332c94e1ef0027b4a94547997eacfcc5e1885f7a53a59c756dda2696
|
|
BLAKE2b-256 checksum How to use checksums |
5bae1b0892095e9dc2b9e2ac7261429e4488ecddeb0ab67c5c315bccdf91192f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | liblathe-0.2.0-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 589.7 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
56fae0ee48d054fc1cd69d13647c80a13e36ee2e6aea7b1c439aa29a2c4124fc
|
|
BLAKE2b-256 checksum How to use checksums |
736da714178a071ed7245c4a3f57cbb92a648f96f418eca9335192f218b290c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl
| Download URL | liblathe-0.2.0-cp311-cp311-macosx_10_9_x86_64.whl |
|---|---|
| Size | 623.8 kB |
| Tags | CPython 3.11 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
c27660684d4ae7653d559656a4051a821dc2e8ca907282b98d5d92c8b1dfe24a
|
|
BLAKE2b-256 checksum How to use checksums |
d0f360f2fad23b1d23eabde79e3ebf0feb5dd908940c4b068a5e4d1f1aee476e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp310-cp310-win_amd64.whl
| Download URL | liblathe-0.2.0-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 756.9 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
e003a1155cb1095d18b93db56254a54992bf2495c6ca3154c5497ba2a26fe000
|
|
BLAKE2b-256 checksum How to use checksums |
4e7ac8234d03001037116e5cd06eb2e369da28e7e6d0212b29fe6fac6137ebf4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp310-cp310-musllinux_1_2_x86_64.whl
| Download URL | liblathe-0.2.0-cp310-cp310-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
e5a75042e47f728b959e8820196f6a86bf385e88d9baa0f578b6621b5b67a753
|
|
BLAKE2b-256 checksum How to use checksums |
4496496bd95e8fa34a9de9a601d258eee55eb8b077cb584ba89ed8c581431c88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | liblathe-0.2.0-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 826.0 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
ab173367c0333d80237c8ba9ed1083c1a56fc2a74e81c84f833f44e4dd4e781c
|
|
BLAKE2b-256 checksum How to use checksums |
6cbf0ea3932db00e15aafe4d64f5335a7328ab8dd368962185d55f2660e5875b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | liblathe-0.2.0-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 583.7 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
c4403a5a79a6c9856f97e5dfbdd93abd16a4e7dc40b55c74beb857a8a19027b8
|
|
BLAKE2b-256 checksum How to use checksums |
51eb472ff5efc05f008b6075de3848624917e2a69c97db5cc90d6c2763617567
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logRelease files / liblathe-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl
| Download URL | liblathe-0.2.0-cp310-cp310-macosx_10_9_x86_64.whl |
|---|---|
| Size | 616.9 kB |
| Tags | CPython 3.10 macOS 10.9+ x86-64 |
|
SHA-256 checksum How to use checksums |
428e4192f7b0c493e75e50e39dc2090d0b9e9873efd721f2a5c6ad5edd5009ba
|
|
BLAKE2b-256 checksum How to use checksums |
48036c4d4d97c2332e2fda2237df9b98f6d839275ece10c23bf98583535f76de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 7, 2026.
Transparency logSecurity for liblathe 0.2.0
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.
Full provenance
All 30 files in this release have been uploaded with provenance metadata.
Attestation for liblathe-0.2.0.tar.gz
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 Nov 7, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
