refactor(log): remove the missing-extra logging fallback

[SkyeAv]

Removes the stdlib-backed logging fallback that stood in for loguru when the optional [log] extra is absent: a base install now produces no logs at all, and loguru (pip install "tablassert[log]") is the only supported logging path.

Logging

• No-op logger: src/tablassert/log.py replaces _StdlibLogger (brace-format shim, append-mode file sink, level table, startup warning) with _NullLogger, which implements exactly the loguru surface tablassert calls — configure/bind/add/remove/info/warning/error/debug — and discards every record.
• No artifacts: LOGASSERT.mkdir() moved inside the loguru branch, so a base install creates no .tablassert/log/, writes no tablassert.log, forwards nothing to the progress display, and emits no "loguru is not installed" warning.
• Unchanged with the extra: the loguru configuration (category bind, 100 MB rotation, enqueue=True, append mode for multiprocessing workers) is untouched, and cli.run()'s logger.add(progress.log_sink, ...) / logger.remove(sink_id) pair keeps working.

Behavior change

• Base installs lose log output. Anything tailing .tablassert/log/tablassert.log on a base install now finds no file, and build-kg --log has no effect. Deliberate: an optional extra should not be shadowed by a second, feature-poor logging implementation.
• Still never fails. [log] remains un-preflighted (extras.require("log") is called nowhere); absence is silent rather than compensated.

Tests

• Rewrote tests/test_log_extra.py around the new contract: the packaging check stays, and the poisoned-sys.modules["loguru"] reload (now also pointing utils.BASE at tmp_path) asserts no directory or file is created, every level is silent under capsys, add/remove are int-returning no-ops, unformattable brace fields cannot raise, and the import emits no logging records or console output. A surface test pins the eight methods tablassert calls so a future call site cannot AttributeError on a base install.
• Updated the doc guards in tests/test_docs_source_of_truth.py: the LOGASSERT.is_dir() live fact is conditional on find_spec("loguru"), and the installation-guide guard pins "no logs" instead of "stdlib".

Docs

• docs/installation.md, docs/cli.md (--log row), docs/tutorial.md, README.md, docs/api/utils.md, llms.txt, and a CHANGELOG.md ## Unreleased → ### Changed entry now describe logging as [log]-only; the historical entry that introduced the fallback is left intact.

Testing

• uv sync --no-default-groups --group ci --extra qc --extra log then uv run pytest → 1337 passed, 43 skipped (src/tablassert/log.py at 100% coverage)
• uv run ruff check . → All checks passed!; uv run ruff format --check . → 88 files already formatted
• uv run pyright → 0 errors, 0 warnings, 0 informations
• Simulated base install (loguru made unimportable via a sys.meta_path blocker): logger is _NullLogger, console output empty, no .tablassert/log created (only .tablassert/store, which utils.py creates unconditionally)
• Rust untouched: no Rust changes, so cargo gates are unaffected.

Questions for the reviewer

• Version bump. Base installs lose .tablassert/log/tablassert.log and --log becomes inert — 19.0.0 material, or a minor since [log] installs are unaffected?

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: d8ec7087-4572-4b08-a8ba-f86315ec7f2a

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}