v0.2.0
·
8 commits
to main
since this release
binquery v0.2.0
v0.2.0 focuses on packaging, automated verification, and clearer documentation. It
does not change the CLI commands, ranking behavior, gates, JSON output, or model.
Highlights
- Moved the Python modules into the dedicated
binquerypackage namespace.
The installedbinquerycommand,python -m binquery, and the repository wrapper
now use the same package entry point. - Added 10 deterministic query unit tests covering routing, ranking, output shape,
limit clamping, duration bonus behavior, and missing-index errors. - Extended GitHub Actions from the existing local indexing check to run the unit
tests and a real-modellavfismoke path through
split -> index -> doctor -> query. - Migrated package licensing metadata to the PEP 639 SPDX form (
MIT) and declared
theLICENSEfile in built distributions. - Improved the README's scope, installation guidance, index-path semantics, output
field descriptions, and rendering portability outside GitHub. - Added a local 10-clip query capture to show the current shortlist output without
presenting it as a large-project or quality benchmark.
Upgrade note
The old top-level Python modules such as cli and query are no longer installed.
They were not a documented library API, but code importing them directly must move
to the binquery namespace. For a source checkout, reinstall the editable package
so the console entry point is regenerated:
python3 -m venv .venv
.venv/bin/pip install -e .The command-line interface remains the supported interface.
Verification
- 10 query unit tests pass on the release commit.
- GitHub Actions passes installation, unit tests, and the real-model synthetic-media
smoke workflow. - The wheel and source distribution build successfully with metadata version 2.4.
- Both distributions pass
twine check. - A clean Python 3.12 environment can install the wheel with all declared
dependencies satisfied and run both help entry points: thebinquerycommand and
python -m binquery.
The lavfi workflow proves that the pipeline runs end to end; it is not a semantic
quality benchmark for real editing footage. See the README for the full scope and
known limitations.