ALPHA
templitz
File templates for faster project bootstrap
Overview
So you’re making another Python project and there are a bunch of boilerplate files you need (use cookiecutter), or you have an existing project that you want to add some stuff to (cookiecutter doesn’t help). templitz offers a very lightweight way to add some typical files to a project.
For example:
$ templitz -t travis
$ templitz -t appveyor
These two commands will dump a typical .travis.yml and a appveyor.yml into your current directory (which should probably be the root of a Python project for any of this to make sense).
This program does nothing other than look up a file with a .templitz extension, and if found, copies that into your target folder. It’s just an easy way to add standard, boilerplate files to projects. Examples are CI configs, setup.py, flit.ini, README.rst, pytest.ini and so on. This tools just does the same copy-from-a-previous-project file copying that you would normally do by hand.
Here are a few more examples:
$ templitz -t asyncio
This one dumps a typical starter main.py for an asyncio-based application.
How about a C/C++? This one will dump a generic Makefile that will work out-of-the-box for most typical C/C++ projects:
$ templitz -t Makefile
BYO templitz
templitz includes a few example templates (in the /library directory), but you can also add your own quite easily: just set the TEMPLITZ_PATH env var to configure your own search path for templates:
$ export TEMPLITZ_PATH=$HOME/.mytemplitz:$HOME/.myothertemplitz
Then your own templitz will be found automatically. Note that the first templit found that matches the given -t parameter is the one that hits, and the TEMPLITZ_PATH setting is checked first.
Reference
$ templitz --help
usage: templitz.py [-h] [-t TEMPLATE] [-i] [-l] [-s] [-o OUTDIR]
[-p PARAMS [PARAMS ...]]
optional arguments:
-h, --help show this help message and exit
-t TEMPLATE, --template TEMPLATE
-i, --info Information about the templit.
-l, --list List all available templitz.
-s, --stdout Write to stdout instead of file.
-o OUTDIR, --outdir OUTDIR
Output directory.
-p PARAMS [PARAMS ...], --params PARAMS [PARAMS ...]
Metadata
Release files for templitz 2017.10.3
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 | |
|---|---|---|---|---|
| templitz-2017.10.3.tar.gz | 11.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| templitz-2017.10.3-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 29.6 kB
Release files / templitz-2017.10.3.tar.gz
| Download URL | templitz-2017.10.3.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33b358b459768cb02471c71cb955cc0a1064ffdac8f99e8b30be477b513eb45a
|
|
BLAKE2b-256 checksum How to use checksums |
12f59e7f1b48a933170a2d91b419384854861675011b04e4b3e8c4d7910c9974
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / templitz-2017.10.3-py2.py3-none-any.whl
| Download URL | templitz-2017.10.3-py2.py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
c062b79d96b2b333bddb3495820c6add9b14d0729aee65c4dde1662b48508c60
|
|
BLAKE2b-256 checksum How to use checksums |
69d72d45f8b47d69cc3b24f33a3eaf2cf9fb43bad4b82ca7104a3926007a7fdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for templitz 2017.10.3
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.