3.0 runs the queue, worker, formatters, redaction, hash chain and the native transports in Rust, and keeps the Python API of
2.0.0. Code that calls Logger, logger.info(...) and the plugins through from logquill import ... needs no change. What
changes is a short list of deliberate behaviours, how the package is installed, and where a few things happen. Each behaviour
is a settled design decision; the number is given for reference in the changelog.
The 3.0 line is MIT licensed; 2.0.0 stays FSL-1.1-MIT as published, and 1.x and earlier stay MIT.
| 2.x | 3.0 | |
|---|---|---|
| Wheel | pure Python | a compiled wheel, one abi3 wheel per platform (Python 3.10 and newer) |
| Python | 3.10 – 3.14 | 3.10 – 3.14, including free-threaded 3.13t / 3.14t |
| Build from source | pip install . |
needs a Rust toolchain (maturin) |
On a platform without a wheel, pip builds the package from the source distribution, which needs Rust. The pure-Python 2.x
line stays on PyPI and on the main branch.
async_dispatch=True is the default. A log call hands the record to a worker
thread and returns. flush() and close() wait for the queue, and an unclosed logger still flushes at exit. To write on
the caller’s thread, as 2.x did by default, pass async_dispatch=False.TamperEvidentPlugin numbers records in write order, so the chain is
valid under many threads. The record a log call returns therefore has no meta.hash yet; the line that is written does.
Read hashes from the file, not from the return value.fails_closed = True to get the same treatment.RedactPlugin matches keys at every depth (D27), and PII scanning covers every non-JSON leaf (D21). Output that used to
keep a nested password now masks it. Compare your redaction tests against real output.\uXXXX-escaped (D32). Split a log file on "\n", not str.splitlines(): splitlines
also breaks on a few Unicode separators that can now appear inside a line.NO_COLOR is unset (D9).Logger writes its queued records and flushes, but no longer closes transports it shares. Close shared
transports yourself.parse_record error text names JSON types (array, number) and quotes with ", because the core is shared.The record shape, schema_version, the llm block, the level weights, the config format, the CLI commands (tail, trace,
serve, dev, verify, installed as the logquill script and also run by python -m logquill.cli) and the canonical JSON the hash chain is computed over are the 2.0 contract. A log file written by
2.0.0 verifies under 3.0, and the reverse. The 3.0 test suite includes oracle tests that run the same scenarios against the
published 2.0.0 and compare the output, with the differences above masked, so nothing else is allowed to change quietly.
Logger("api", meta={...}): fixed meta on every record, inherited by children.install_signal_handlers(log): on SIGTERM or SIGINT, drain the queue, then exit with 128 plus the signal.logquill.bridges.loguru_sink and structlog_processor, and logquill.tracing.otel_span_processor.OtelSpanProcessor.bindings/python/bench/compare.py).splitlines, redaction of nested keys, and the content-off placeholder; those are the places a
behaviour change shows up as a test failure.meta.hash from a returned record, read it from the written line instead.async_dispatch=False or call flush() where you need the line on
disk.logquill verify FILE; it should pass unchanged.