Python Checkpointed Local Log
Install from this directory with pip install . or pip install -e ".[dev]".
The installed package is cll, including checkpoint, ledger, log,
revocation and signing; the command is cll. From the repository root, use
pip install ./python. Run tests here with uv run --extra dev pytest.
CLL storage backends
cll.log implements the CLL backend contract
shared with Go and TypeScript: the EntrySource, EntryStore,
CheckpointStateStore, WitnessStateStore, CheckpointStore and Backend
protocols, their values and error classes, and four backends.
| Module | Backend | Lifecycle |
|---|---|---|
cll.log.memory |
MemoryStore, in process |
constructor |
cll.log.jsonl |
JSONL v4 journal, single writer (POSIX flock) |
init(path), open(path) |
cll.log.sqlite |
shared SQLite schema, stdlib sqlite3 |
init(path, log_id), open(path, log_id) |
cll.log.mysql |
shared MySQL 8 schema, PyMySQL | init(url, log_id), open(url, log_id) |
from datetime import datetime, timezone
from cll.log import AppendInput, jsonl
jsonl.init("cll.jsonl")
store = jsonl.open("cll.jsonl")
result = store.append(AppendInput(bytes(32), datetime.now(timezone.utc)))
store.close()
The JSONL, SQLite and MySQL formats interoperate with Go and TypeScript: a log
any of them writes opens, continues and verifies in the others. The MySQL
backend needs the mysql extra (pip install ".[mysql]"); its target is a
mysql://user:password@host:port/database URL. Importing cll or cll.log
loads no database driver.
cll.log.conformance runs the shared conformance vectors against any backend,
including your own; see its module docstring. cll.log.ledger puts the
Python-specific LedgerStore behind EntryStore (without bare-identity
append) and any LogSource behind EntrySource.
The MySQL tests read CLL_MYSQL_URL and skip when it is unset, except under
CI, where they fail.
The authoritative specification and shared vectors live at the repository root. See the repository README for API and trust boundaries.
Metadata
Release files for checkpointed-local-log 0.6.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 | |
|---|---|---|---|
| checkpointed_local_log-0.6.0.tar.gz | 117.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| checkpointed_local_log-0.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 250.7 kB
Release files / checkpointed_local_log-0.6.0.tar.gz
| Download URL | checkpointed_local_log-0.6.0.tar.gz |
|---|---|
| Size | 117.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
531e4fdb38e6a3c441c1bed22af7d0a5817bd25eb839a2f6b1aa09d406feaee8
|
|
BLAKE2b-256 checksum How to use checksums |
faa6d2947453f370f87bb341ec0c603381044bc9ea9851c1852f68067c9bb21f
|
| 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 15, 2026.
Transparency logRelease files / checkpointed_local_log-0.6.0-py3-none-any.whl
| Download URL | checkpointed_local_log-0.6.0-py3-none-any.whl |
|---|---|
| Size | 133.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f70e877779222f71964d26da2b7ac235b5d12b2a1d727e6003d4e9310ec04dc7
|
|
BLAKE2b-256 checksum How to use checksums |
58d8666b720d422232dbfc609743c2031e525d2daf804af387212fb7feed7fa1
|
| 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 15, 2026.
Transparency log