piecutter
#########
.. raw:: html
<a href="http://badge.fury.io/py/piecutter"><img src="https://badge.fury.io/py/piecutter.png"></a>
<a href="https://travis-ci.org/diecutter/piecutter"><img src="https://travis-ci.org/diecutter/piecutter.png?branch=master"></a>
<a href="https://crate.io/packages/piecutter?version=latest"><img src="https://pypip.in/d/piecutter/badge.png"></a>
`piecutter` is a template rendering framework, written in `Python`_.
Leitmotiv: **render templates against context**, wherever the templates,
whatever the template engine.
**************
Project status
**************
`piecutter` is under active development.
**Yesterday**, `piecutter` was the core of `diecutter`_.
As `diecutter`'s authors, we think `diecutter` has great features related to
templates and file generation. We wanted to share it with a larger audience.
So we just packaged it as a standalone library.
And we are planning to make it better as soon as possible.
`Join us`_ if you like the features ;)
Here are some of our motivations:
* third-party projects can use `piecutter`. They do not have to depend on
`diecutter`, which embeds some specific code related to its web service.
* as a standalone library, `piecutter` should be easier to maintain and
improve.
* `piecutter` is more open than `diecutter`. It can have a larger community.
It also may converge with similar tools.
**Today**, `piecutter` is tied to `diecutter` implementation. The API
reflects `diecutter`'s architecture and concepts, which may sound obscure for
other usage.
**Tomorrow**, we are planning to improve `piecutter`. As an example, we think
the API should be refactored, with simplicity in mind.
************
Key features
************
* Simple API: render templates against context.
* Support multiple template engines: `Jinja2`_ and `Django`_ for now. Later:
`Cheetah`_ and even non-Python template engines such as Ruby's `ERB`_.
* Render files and directories.
* Load templates from almost everywhere: local filesystem and github.com for
now. Later: Django storages...
* Do what you want with generated content: write to local filesystem, generate
an archive...
*********
Resources
*********
* Documentation: https://piecutter.readthedocs.org
* PyPI page: http://pypi.python.org/pypi/piecutter
* Bugtracker: https://github.com/diecutter/piecutter/issues
* Changelog: https://piecutter.readthedocs.org/en/latest/about/changelog.html
* Roadmap: https://github.com/diecutter/piecutter/issues/milestones
* Code repository: https://github.com/diecutter/piecutter
* Continuous integration: https://travis-ci.org/diecutter/piecutter
.. _`Python`: https://python.org
.. _`diecutter`: http://diecutter.io
.. _`join us`: https://piecutter.readthedocs.org/en/latest/contributing.html
.. _`Jinja2`: http://jinja.pocoo.org/
.. _`Django`: https://djangoproject.com
.. _`Cheetah`: http://pythonhosted.org/Cheetah/
.. _`ERB`: http://ruby-doc.org/
Metadata
Release files for piecutter 0.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 | |
|---|---|---|---|---|
| piecutter-0.1.1.zip | 26.3 kB | Without provenance | Details |
Release files / piecutter-0.1.1.zip
| Download URL | piecutter-0.1.1.zip |
|---|---|
| Size | 26.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
efa5385e28e06e8097eaa968c938ebeac44d16f3571899580baa84c2522127dd
|
|
BLAKE2b-256 checksum How to use checksums |
404401cba94b6e880085cb217cdad25f472be427dcb9a5028185fc19083371d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for piecutter 0.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.