fanbase-cli
The fanbase command: browse, install and update grammars from the Fanbase registry.
The registry itself lives in the fanbase
repository; this package is the client. You never need the whole registry: a spec is
fetched when you ask for it, and fetched again only when the registry has a newer one.
Install
pip install fanbase
Fandango depends on fanbase, so pip install fandango-fuzzer installs it too.
Using specs with Fandango
fandango -F NAME is fandango -f FILE, for a spec from the registry. The spec is fetched
into Fandango's standard library location if it is missing or out of date, and then used:
fandango fuzz -F png -n 10 # the default PNG spec; writes png-inputs/fandango-0000.png ...
fandango fuzz -F png-apng -n 10 -d apngs # a named variant, into a directory of your choice
fandango fuzz -F png -f mypng.fan -n 10 # your own rules on top of the Fanbase spec
Since the format is known, the file name extension is set for you, and with neither -o
nor -d the files go to a fresh directory (png-inputs, then png-inputs-2, ...). Every
other fandango fuzz option works as usual. See the Fandango documentation for details.
A first look
fanbase list # the formats in the registry
fanbase list png # the specs of one format
fanbase show png-apng # one spec's metadata
fanbase install png-apng # copy it where Fandango's include() finds it
What else it does
| You want to | Commands | Read |
|---|---|---|
| find, install and update specs | list, search, show, install, update, uninstall, outdated, diff, cite |
Using specs |
| run with exactly the specs you used before | lock, install --locked |
Repeating a run |
| write a spec and contribute it | new, fork, rebase, deps, check, changes, publish |
Writing specs |
| see how well a spec's files do against real parsers | evaluate, targets, quality |
Evaluating a spec |
| keep what a parser does on a bad file private | incidents open, send, list, show, track, tracked, verify |
The private record |
| use another registry, or run your own | registry, pin, unpin, reindex |
Registries |
| sign a registry, put it on a site, give a spec a DOI | sign, verify, site, doi |
Signing, browsing and citing |
fanbase --help lists every command, and fanbase COMMAND --help its options.
License
Apache-2.0, see LICENSE.
Metadata
Release files for fanbase 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fanbase-0.5.0.tar.gz | 212.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fanbase-0.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 342.4 kB
Release files / fanbase-0.5.0.tar.gz
| Download URL | fanbase-0.5.0.tar.gz |
|---|---|
| Size | 212.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ecfecd28be785cae7ea6b21f74d4990bca5206aabff4958b9ac20ea7e041c052
|
|
BLAKE2b-256 checksum How to use checksums |
9d85861ff2631bad1039836971989559f00608a55f48d5e867f104572bdf5227
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / fanbase-0.5.0-py3-none-any.whl
| Download URL | fanbase-0.5.0-py3-none-any.whl |
|---|---|
| Size | 130.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eccac34d0f8f814398a7eb64c3c6608309a264a7c28dce209bc7edc161ea96b3
|
|
BLAKE2b-256 checksum How to use checksums |
e091252ca33335c13875d467595d13c564aef836ba1e3a0f11c6b5f8536c8ace
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|