# jinjarg
CLI-template renderer like m4 but based on jinja2 and argparse.
## Installation
` shell pip install jinjarg `
## Usage example
Take a look at [example](/example) directory.
## Why
There is jinja-cli and it’s fine… until you need logic that doesn’t fit in Jinja.
1 maintainer
Metadata
1 maintainer
Release files for jinjarg 0.1.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 | Provenance | |
|---|---|---|---|---|
| jinjarg-0.1.0.tar.gz | 2.7 kB | Without provenance | Details |
Release files / jinjarg-0.1.0.tar.gz
| Download URL | jinjarg-0.1.0.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a7eca5b030ebd72b0fe854346f8c133e38809cd5d47096833c2f2623692f9455
|
|
BLAKE2b-256 checksum How to use checksums |
24a4ba4d2976e5637c27816eff5261845df5609c2891c0b764fbae47e8c3a216
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.0
|
Security for jinjarg 0.1.0
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.
