===================
A simple command-line tool for convenient templates processing. For example, you have a config file for some web service and just want to put there a different host:port binding
depending on the target server role. Using the tool, you can simply pass the missing variables using syntax like:
```bash
clt --tpl your_file.conf --out test.out --binding 127.0.0.1:9999
```
Examples
--------
Reads infile.tpl template and rewrites its contents to infile.out,
substituting "$$$test":
```bash
clt --tpl infile.tpl --out file.out --delim '$$$' --test 30
```
Reads infile.tpl template and rewrites its contents to outdir/infile.tpl,
substituting "%var1" and "%var2":
```bash
clt --tpl infile.tpl --out outdir --delim '%' --var1 20 --var2 hello
```
Reads all files from indir and rewrites them to outdir,
substituting "$$$var1" and "$$$var2" ("$$$" is the default delimiter):
```bash
clt --tpl indir --out outdir --var1 10 --var2 50
```
Reads all files matching "*.tpl" and rewrites them to
outdir, substituting "$$$var1" and "$$$var2":
```bash
clt --tpl indir/\*.tpl --out outdir --var1 10 --var 20
```
Installation
------------
```bash
pip install clt
```
Python versions supported
------------
Tested with 2.6.x and 2.7.x
Metadata
Release files for clt 1.1
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 | |
|---|---|---|---|---|
| clt-1.1.tar.gz | 3.0 kB | Without provenance | Details |
Release files / clt-1.1.tar.gz
| Download URL | clt-1.1.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
296db0741a85f102c6e99ab0d09de842d8bc12d3a622f6cdd8a702cb29baee30
|
|
BLAKE2b-256 checksum How to use checksums |
769b84a5231e09baf0c87311a1f3010fcda8aac7a1e7ed967ccee42ae5b156eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for clt 1.1
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.