gnomish-army-knife (1.5.8)
World of Warcraft polyfills and standardization.
Consider sponsoring development.
Python Version Support
This package is tested with the following Python minor versions:
Platform Support
This package is tested on the following platforms:
ubuntu-latestmacos-latestwindows-latest
Introduction
LUA source hosted here for CurseForge integration.
Command-line Options
$ ./venv3.14/bin/gak -h
usage: gak [-h] [--version] [-v] [-q] [--curses] [--no-uvloop] [-C DIR]
{markdown,scan,noop} ...
World of Warcraft polyfills and standardization.
options:
-h, --help show this help message and exit
--version show program's version number and exit
-v, --verbose set to increase logging verbosity
-q, --quiet set to reduce output
--curses whether or not to use curses.wrapper when starting
--no-uvloop whether or not to disable uvloop as event loop driver
-C, --dir DIR execute from a specific directory
commands:
{markdown,scan,noop} set of available commands
markdown generate Markdown content from class data
scan scan the 'World of Warcraft' directory for updates
noop command stub (does nothing)
Sub-command Options
markdown
$ ./venv3.14/bin/gak markdown -h
usage: gak markdown [-h] [-o OUTPUT] [-d DATABASE]
options:
-h, --help show this help message and exit
-o, --output OUTPUT output directory (default: 'gnomish-army-knife-
markdown')
-d, --database DATABASE
macro database (default:
'package://gnomish_army_knife/macros.yaml')
scan
$ ./venv3.14/bin/gak scan -h
usage: gak scan [-h] [-c CONFIG] [-s STATE] [-e]
options:
-h, --help show this help message and exit
-c, --config CONFIG path to an optional configuration file (default:
'gak.yaml')
-s, --state STATE path to the program's state directory (default:
'/home/vkottler/.local/state/gak')
-e, --ephemeral set to use new, temporary directories when applicable
Internal Dependency Graph
A coarse view of the internal structure and scale of
gnomish-army-knife's source.
Generated using pydeps (via
mk python-deps).
Metadata
Release files for gnomish-army-knife 1.5.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gnomish_army_knife-1.5.8.tar.gz | 2.5 MB | Without provenance | Details for gnomish_army_knife-1.5.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gnomish_army_knife-1.5.8-py3-none-any.whl | Python 3 | none | any | Details for gnomish_army_knife-1.5.8-py3-none-any.whl |
Total release size: 5.2 MB
Release files / gnomish_army_knife-1.5.8.tar.gz
| Download URL | gnomish_army_knife-1.5.8.tar.gz |
|---|---|
| Size | 2.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f91efaef4d8f305180f1e29dc326a44dfa12d6b40e457384724f1370bfc448d8
|
|
BLAKE2b-256 checksum How to use checksums |
fe21d3458904e44fa650c2bf58fdd935a1f2635a8cbd84d7d79f6d792ed7e544
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / gnomish_army_knife-1.5.8-py3-none-any.whl
| Download URL | gnomish_army_knife-1.5.8-py3-none-any.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
27df882c7bc1e3e6d85c6d4f630ee4a2f4da0cbf74eab547059a4915a2edc73f
|
|
BLAKE2b-256 checksum How to use checksums |
6f222a9f095b5f780bed62454c712e93d1dee677b9dd18d2e3e676bd44023681
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for gnomish-army-knife 1.5.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.