logquill

Migrating from logquill 2.x to 3.0 (Python)

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.

1. Install

  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.

2. Behaviour that changed

3. What did not change

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.

4. New in 3.0

5. Checklist

  1. Install the 3.0 wheel into a fresh environment and run your test suite.
  2. Search your tests for splitlines, redaction of nested keys, and the content-off placeholder; those are the places a behaviour change shows up as a test failure.
  3. If you read meta.hash from a returned record, read it from the written line instead.
  4. If you relied on a log call being synchronous, pass async_dispatch=False or call flush() where you need the line on disk.
  5. Verify an existing log with logquill verify FILE; it should pass unchanged.