Skip to main content

LibLathe Python package codecov PyPI Python versions

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:

  1. 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.
  2. 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:

Facing Example

Roughing:

Roughing Example

Profiling:

Profiling Example

Parting:

Parting Example

Metadata

Release files for liblathe 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for liblathe 0.1.0
File Size Uploaded Provenance Actions
liblathe-0.1.0.tar.gz 50.5 kB With provenance Details for liblathe-0.1.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for liblathe 0.1.0
File Actions
liblathe-0.1.0-pp310-pypy310_pp73-win_amd64.whl PyPy 3.10 PyPy 3.10 7.3 Windows x86-64 Details for liblathe-0.1.0-pp310-pypy310_pp73-win_amd64.whl
liblathe-0.1.0-pp310-pypy310_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl PyPy 3.10 PyPy 3.10 7.3 Linux glibc 2.17+ x86-64 Details for liblathe-0.1.0-pp310-pypy310_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
liblathe-0.1.0-cp313-cp313-win_amd64.whl CPython 3.13 CPython 3.13 Windows x86-64 Details for liblathe-0.1.0-cp313-cp313-win_amd64.whl
liblathe-0.1.0-cp313-cp313-musllinux_1_2_x86_64.whl CPython 3.13 CPython 3.13 Linux musl 1.2+ x86-64 Details for liblathe-0.1.0-cp313-cp313-musllinux_1_2_x86_64.whl
liblathe-0.1.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.13 CPython 3.13 Linux glibc 2.17+ x86-64 Details for liblathe-0.1.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
liblathe-0.1.0-cp313-cp313-macosx_11_0_arm64.whl CPython 3.13 CPython 3.13 macOS 11.0+ ARM64 Details for liblathe-0.1.0-cp313-cp313-macosx_11_0_arm64.whl
liblathe-0.1.0-cp313-cp313-macosx_10_13_x86_64.whl CPython 3.13 CPython 3.13 macOS 10.13+ x86-64 Details for liblathe-0.1.0-cp313-cp313-macosx_10_13_x86_64.whl
liblathe-0.1.0-cp312-cp312-win_amd64.whl CPython 3.12 CPython 3.12 Windows x86-64 Details for liblathe-0.1.0-cp312-cp312-win_amd64.whl
liblathe-0.1.0-cp312-cp312-musllinux_1_2_x86_64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ x86-64 Details for liblathe-0.1.0-cp312-cp312-musllinux_1_2_x86_64.whl
liblathe-0.1.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.17+ x86-64 Details for liblathe-0.1.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
liblathe-0.1.0-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details for liblathe-0.1.0-cp312-cp312-macosx_11_0_arm64.whl
liblathe-0.1.0-cp312-cp312-macosx_10_13_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.13+ x86-64 Details for liblathe-0.1.0-cp312-cp312-macosx_10_13_x86_64.whl
liblathe-0.1.0-cp311-cp311-win_amd64.whl CPython 3.11 CPython 3.11 Windows x86-64 Details for liblathe-0.1.0-cp311-cp311-win_amd64.whl
liblathe-0.1.0-cp311-cp311-musllinux_1_2_x86_64.whl CPython 3.11 CPython 3.11 Linux musl 1.2+ x86-64 Details for liblathe-0.1.0-cp311-cp311-musllinux_1_2_x86_64.whl
liblathe-0.1.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.11 CPython 3.11 Linux glibc 2.17+ x86-64 Details for liblathe-0.1.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
liblathe-0.1.0-cp311-cp311-macosx_11_0_arm64.whl CPython 3.11 CPython 3.11 macOS 11.0+ ARM64 Details for liblathe-0.1.0-cp311-cp311-macosx_11_0_arm64.whl
liblathe-0.1.0-cp311-cp311-macosx_10_9_x86_64.whl CPython 3.11 CPython 3.11 macOS 10.9+ x86-64 Details for liblathe-0.1.0-cp311-cp311-macosx_10_9_x86_64.whl
liblathe-0.1.0-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for liblathe-0.1.0-cp310-cp310-win_amd64.whl
liblathe-0.1.0-cp310-cp310-musllinux_1_2_x86_64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ x86-64 Details for liblathe-0.1.0-cp310-cp310-musllinux_1_2_x86_64.whl
liblathe-0.1.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ x86-64 Details for liblathe-0.1.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
liblathe-0.1.0-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for liblathe-0.1.0-cp310-cp310-macosx_11_0_arm64.whl
liblathe-0.1.0-cp310-cp310-macosx_10_9_x86_64.whl CPython 3.10 CPython 3.10 macOS 10.9+ x86-64 Details for liblathe-0.1.0-cp310-cp310-macosx_10_9_x86_64.whl

Total release size: 18.7 MB

Release files / liblathe-0.1.0.tar.gz

Download URL liblathe-0.1.0.tar.gz
Size 50.5 kB
Tags Source
SHA-256 checksum
How to use checksums
5bfb610751996c955338b8205d346e167279711026a1e8eca976ba5791ca4cf1
BLAKE2b-256 checksum
How to use checksums
26feee13c3b3939501f0592cdd13700f298992d09792c97701e8846c58d14d2b
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-pp310-pypy310_pp73-win_amd64.whl

Download URL liblathe-0.1.0-pp310-pypy310_pp73-win_amd64.whl
Size 571.9 kB
Tags PyPy 3.10 PyPy 3.10 7.3 Windows x86-64
SHA-256 checksum
How to use checksums
5b3b2ce703ba291ae8f95b3a31168808b7f07c3dd3921110943db07f579bc921
BLAKE2b-256 checksum
How to use checksums
5dcf18d84e87dff1ceb04fe9250eecb365ebe577e5fc973d489e98a6b2a260a1
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-pp310-pypy310_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL liblathe-0.1.0-pp310-pypy310_pp73-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 777.3 kB
Tags Linux glibc 2.17+ x86-64 PyPy 3.10 PyPy 3.10 7.3
SHA-256 checksum
How to use checksums
2a7f0f9ccb49782b213d802715020fdbcb9196e2bbb21a763cd35dac40bef326
BLAKE2b-256 checksum
How to use checksums
90e0dee7974c8cd72f2de13053c3e2da19ff0dbd9e10fbb98e790099b192ba87
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp313-cp313-win_amd64.whl

Download URL liblathe-0.1.0-cp313-cp313-win_amd64.whl
Size 582.5 kB
Tags CPython 3.13 Windows x86-64
SHA-256 checksum
How to use checksums
58af9098b7a4ebd4101fe1ac68342fbdb5d076c05bd30a0f8f66cce5c07f0c37
BLAKE2b-256 checksum
How to use checksums
fa579fac66f1c5917505fb96e42d9c07c4e796b0e3bfb1de100473699e08d411
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp313-cp313-musllinux_1_2_x86_64.whl

Download URL liblathe-0.1.0-cp313-cp313-musllinux_1_2_x86_64.whl
Size 1.7 MB
Tags CPython 3.13 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
c37af7a586636a26b9fa274c0be3e669ffda0ce21fde5e84797ae6b0d34b78f7
BLAKE2b-256 checksum
How to use checksums
19cacf71ad3f278f7b7b9c96bb5ee6c7fe79185e11bdecf573f917490a14a1d9
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL liblathe-0.1.0-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 834.9 kB
Tags CPython 3.13 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
bdeb56188db42c7701f7c354b032233228006bb976e2c868afc9ac730defc258
BLAKE2b-256 checksum
How to use checksums
fd232630128d5480a8ef6437d70e8a13d0211c9ce327c15f88a508ba56c9508f
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp313-cp313-macosx_11_0_arm64.whl

Download URL liblathe-0.1.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
a0faa10603050122614177251b71a45816d6479a91255e9f53104c6a0dbd3563
BLAKE2b-256 checksum
How to use checksums
609df74fc057d7e73a040c7cb3084ffe4eb3bfddd09fecd0b5dc4a6a1f0bfb80
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp313-cp313-macosx_10_13_x86_64.whl

Download URL liblathe-0.1.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
a7eb020fd64b1277d52f0db704575ad3ab08da44876d2a142bc93a58beaa9340
BLAKE2b-256 checksum
How to use checksums
24a5e7c89f06743b06346c37c4a4833955a2e5b9f6f65503281c06ce19dc9fc7
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp312-cp312-win_amd64.whl

Download URL liblathe-0.1.0-cp312-cp312-win_amd64.whl
Size 582.4 kB
Tags CPython 3.12 Windows x86-64
SHA-256 checksum
How to use checksums
7e2041cb718133979fefb3487956025b553d6f2dec12be5a1f8d16f10ee4b658
BLAKE2b-256 checksum
How to use checksums
0293fc25aac12710569a914e5bd84c1a5d3cb31eaefbca0b9f78c59726523e46
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL liblathe-0.1.0-cp312-cp312-musllinux_1_2_x86_64.whl
Size 1.7 MB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
68f729ee09beab34938099330904b6d2df2e91c7f2e3e8b019748d4eb114027d
BLAKE2b-256 checksum
How to use checksums
3d9cbb5b142f58017cef862491373b9d6518a1113917903a7696079a13d37d61
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL liblathe-0.1.0-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 834.5 kB
Tags CPython 3.12 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
490b283c26f2b595d9dea43004dfe1ac2ac8b31f681adc4a23d4437520fc863e
BLAKE2b-256 checksum
How to use checksums
a35ed478ecca267b7b869001849d9d3a62c2b9f84462c532eb6bd3df5b516129
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp312-cp312-macosx_11_0_arm64.whl

Download URL liblathe-0.1.0-cp312-cp312-macosx_11_0_arm64.whl
Size 590.9 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
42a825581474a19a2e29560b14efde6a463d3154c767a6d3b7679e2f45abf1fc
BLAKE2b-256 checksum
How to use checksums
2fefb12bc5bd1da3a80bcb2c36a910936637c07468ea3e34593c7fba0ca12d3b
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp312-cp312-macosx_10_13_x86_64.whl

Download URL liblathe-0.1.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
76a3d74ee9663c4fbf9c86a0c8af068b88dfb8b7a27b850113a18db3b91e4075
BLAKE2b-256 checksum
How to use checksums
761f9daafee9a9f5b1f8c46cc48eba0df111afea9e6f96294f82aaad547a54d7
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp311-cp311-win_amd64.whl

Download URL liblathe-0.1.0-cp311-cp311-win_amd64.whl
Size 573.8 kB
Tags CPython 3.11 Windows x86-64
SHA-256 checksum
How to use checksums
16d0963c57f59768dd8d486dceb72c31848c5471f96ab08ac23661b1e97e2dcd
BLAKE2b-256 checksum
How to use checksums
0aaa744bb8077efd661a01b56e10d41b70693122e14032a08129fd022e371ed6
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp311-cp311-musllinux_1_2_x86_64.whl

Download URL liblathe-0.1.0-cp311-cp311-musllinux_1_2_x86_64.whl
Size 1.7 MB
Tags CPython 3.11 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
b12e65e1c38d27ff39488ba644e31084061f95c5523a38e748606dd3be4620c2
BLAKE2b-256 checksum
How to use checksums
e1d241a86f221b21cecea8432fb554fdb3ce1a314a86e83df2466dac2cb11870
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL liblathe-0.1.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 833.4 kB
Tags CPython 3.11 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
51393b3d8e586df697d60cf9eb262a659785397ca212b61a6a5b710564cc69d3
BLAKE2b-256 checksum
How to use checksums
7c4d3918686e5be0bf0b2ef13dc4d90de4ea5571eb1715ba5d40311cd7cba1ee
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp311-cp311-macosx_11_0_arm64.whl

Download URL liblathe-0.1.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
9ab09d5d28c78bd6021981b673ba4cb9443b3bce1b6a275fd408d25d0672fb66
BLAKE2b-256 checksum
How to use checksums
9a7a4f84519005dc8121a252731723cdd3ba93b668e46836ed4be9309d51cab4
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp311-cp311-macosx_10_9_x86_64.whl

Download URL liblathe-0.1.0-cp311-cp311-macosx_10_9_x86_64.whl
Size 623.7 kB
Tags CPython 3.11 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
26f3e9539b7dddf63274cc30cd2406604ed56c02e4be813e2478c5dc5858dd88
BLAKE2b-256 checksum
How to use checksums
eaa66933cebf48012b76bb83d5d27ae909f13e4001ec13417713ae1713103df6
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp310-cp310-win_amd64.whl

Download URL liblathe-0.1.0-cp310-cp310-win_amd64.whl
Size 569.9 kB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
b7114854fd072740356afd1cdb33ce7b2f80a5b1475775538898d5d2814753ea
BLAKE2b-256 checksum
How to use checksums
5b2001df54e301ec78127e051f73103ccd824a6740429bbd0e278dcaa84df542
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp310-cp310-musllinux_1_2_x86_64.whl

Download URL liblathe-0.1.0-cp310-cp310-musllinux_1_2_x86_64.whl
Size 1.7 MB
Tags CPython 3.10 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
73b0849966d2774566aeef2de1400cc1f4505c3ed1a6aea760f3a1c8f11fcb0e
BLAKE2b-256 checksum
How to use checksums
456e57a7c346f31629d9469d8fc7af09c8084f4d14eab488ed330bc0372985ed
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL liblathe-0.1.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 826.0 kB
Tags CPython 3.10 Linux glibc 2.17+ x86-64
SHA-256 checksum
How to use checksums
116603c67ca5e58427e591b558844d27fcc4d58c8f675da8474e1f44463f0407
BLAKE2b-256 checksum
How to use checksums
660ae7e9010070728ad2b1c594dc27258f7c632b424eff9910ffe2c60cf0f1bb
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp310-cp310-macosx_11_0_arm64.whl

Download URL liblathe-0.1.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
7f9001a99162001ab602b9adf6923495f065f127f57ea86a41bf296bf42c27ac
BLAKE2b-256 checksum
How to use checksums
2a37290a8cc0bc64c49fb2d84889c433d65ab3e208a0f95c175ffb48565197ac
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 6, 2026.

Transparency log

Release files / liblathe-0.1.0-cp310-cp310-macosx_10_9_x86_64.whl

Download URL liblathe-0.1.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
b6fda37663f5011e0fe53fcbb78bdc47cf17101d484137a1c9469919bf57c56e
BLAKE2b-256 checksum
How to use checksums
13b35959c48f0b1792cde0177fd533764830a90618597fd61bf03f3b5b92b20c
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 6, 2026.

Transparency log

Security for liblathe 0.1.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 23 files in this release have been uploaded with provenance metadata.

Select from 23 files

Attestation for liblathe-0.1.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 6, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page