fanbase 0.6.0

fanbase 0.6.0

• Releasing: a release is made by pushing a tag. The tests (Linux, macOS, Windows) run first, then PyPI, and the GitHub release comes last. A release made by hand on GitHub no longer uploads to PyPI (RELEASING.md).
• evaluate --reuse FILE|URL: a spec that nothing it depends on has changed for is not evaluated again. Each spec in quality.json carries a fingerprint of the spec and what it extends, its parsers (files and versions), Fandango, fanbase and the settings. Use one seed.
• The files that evaluate and check ask Fandango for have the extension of their format (.png), as under fandango -F.
• Speeds under 1 file per second show their digits (0.05/s, not 0/s).
• Windows: diff compares bytes, so a spec with CRLF line endings no longer shows every line changed (this affected every system); the files of a registry are always written with LF; a target whose command cannot be started is an error verdict and no longer stops the evaluation; messages name registry paths with /.
• The README is a short front page, with one page per topic in docs/.

v0.5.0

Tools for writing, checking and publishing specs, and for judging how well they do. The README describes every command.

• Using specs: uninstall, list --installed, outdated, diff, search, cite, --json, fanbase.lock, and a warning when the installed Fandango is outside a spec's fandango range. On a Mac, specs are now installed in ~/Library/Fandango, which Fandango searches first.
• Registries: more than the public one, with names, pins and an explicit decision to trust; a spec can extends other specs, with version ranges.
• Writing specs: new, fork (and fork --with-deps), check (-j N, --changed), changes, publish, and rebase, which also merges the original's metadata changes.
• Evaluating specs: evaluate runs a spec's files through the parsers of its format and can measure how much of a parser they reach (--coverage); quality.json and --compare-with say what changed. What a parser does on a generated file goes to a private, encrypted record (incidents open|send|list|show|track|verify).
• Publishing: doi (Zenodo), site (a static page for a registry), and sign / verify (SSH signatures on a registry's index).

fanbase 0.4.2

Adds fanbase install --all, and installs the Python packages a spec needs (install, update and fandango -F; --no-requirements skips it). A spec's metadata can list pip requirements for packages that are not named like their module.

fanbase 0.4.1

PyPI metadata: a clearer description, keywords, classifiers and project links. No other changes.

fanbase 0.4.0

Registry client: list, show, install, update and reindex. Default registry, offline fallback, and the API behind fandango -F.