azcat
azcat is an alternative to cat(1); specialized for printing. It prints files with syntax highlighting and formatting.
Installation
$ pip3 install azcat # use Python3
Usage
$ az --help # manual
$ az /usr/local/bin/az
$ az README.md
$ az -t main # source code reading with GNU global(1)
$ az -F timetable.csv # pretty printing
$ az -P story.md # read with less(1)
$ curl example.com/api/foo.json | az -f json
License
azcat is a public domain software.
Contributors
Seiya Nuta: Author
Alessandro Pisa: PR #3
Simeon Visser: PR #7
Marc Abramowitz: PR #12
Contributing
Please send a Pull Request on GitHub. I will be very happy whatever the PR does :)
Metadata
Release files for azcat 1.0.5
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 |
|---|---|---|---|---|
| azcat-1.0.5.tar.gz | 4.9 kB | Without provenance | Details for azcat-1.0.5.tar.gz |
Release files / azcat-1.0.5.tar.gz
| Download URL | azcat-1.0.5.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9cc540db809bafeb33f135db1df5aedcee69ad12c8714e0ec4d3f631cf43ef82
|
|
BLAKE2b-256 checksum How to use checksums |
b04fc1efe0e2b5b72f5b3eac7ac443f6d2436b88f1385d8d8a9acda07697902b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for azcat 1.0.5
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.