apertium-lint
linter for Apertium source files
This package provides the command-line tool apertium-lint which statically analyzes Apertium source files for potential issues.
The linter can be run on a single file, giving output like
$ apertium-lint modes.xml
modes.xml
Error (install-deps) on line 8: Debug modes using files in .deps/ should not be installed.
Error (install-deps) on line 25: Debug modes using files in .deps/ should not be installed.
Error (install-deps) on line 91: Debug modes using files in .deps/ should not be installed.
Errors: 3 Warnings: 0 Suggestions: 0 Nitpicks: 0
or it can be run without arguments, which will apply it to the entire current directory
$ apertium-lint
./modes.xml
Error (install-deps) on line 8: Debug modes using files in .deps/ should not be installed.
Error (install-deps) on line 25: Debug modes using files in .deps/ should not be installed.
Error (install-deps) on line 91: Debug modes using files in .deps/ should not be installed.
./paper/paper.tex
Warning (unnorm) on line 113: Line contains non-normalized characters.
Errors: 3 Warnings: 1 Suggestions: 0 Nitpicks: 0
With option -s, statistics about the files will also be gathered.
$ apertium-lint -s apertium-kir.kir.twol
apertium-kir.kir.twol
Input alphabet symbols: 169
Output alphabet symbols: 139
Rules: 61
Sets: 35
Alphabet symbol pairs: 169
Errors: 0 Warnings: 0 Suggestions: 0 Nitpicks: 0
Prerequisites:
- python 3
- pip or pipx (see https://pipx.pypa.io/latest/installation/ for how to install pipx on Debian/Ubuntu/Macos etc.)
Installation:
If you have pipx installed, you can just do:
$ pipx install apertium-lint
(Alternatively, pip install apertium-lint should also work, but plain pip can make a bit of a mess if you have lots of packages installed on your user.)
Metadata
Release files for apertium-lint 1.0.12
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 |
|---|---|---|---|---|
| apertium_lint-1.0.12.tar.gz | 35.0 kB | Without provenance | Details for apertium_lint-1.0.12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| apertium_lint-1.0.12-py3-none-any.whl | Python 3 | none | any | Details for apertium_lint-1.0.12-py3-none-any.whl |
Total release size: 77.1 kB
Release files / apertium_lint-1.0.12.tar.gz
| Download URL | apertium_lint-1.0.12.tar.gz |
|---|---|
| Size | 35.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef967e635e2905e9a8332425bed601754965392a10371c5f5ff68fda4c4277a3
|
|
BLAKE2b-256 checksum How to use checksums |
189b5c0f88da13fa7cafbe7b3382e66f7f82aee33d4b0d6028b6aebfd00ef7bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Release files / apertium_lint-1.0.12-py3-none-any.whl
| Download URL | apertium_lint-1.0.12-py3-none-any.whl |
|---|---|
| Size | 42.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
47832a83a9347a0bbb16cfa4b20a7e5929b53b9cb07eaea511723626ce8de33c
|
|
BLAKE2b-256 checksum How to use checksums |
1933e2c2fce01f8c41fe0b9e77a7f421524df379b7f4d8f0192986132c4e4856
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for apertium-lint 1.0.12
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.