jinjanator-plugin-format-toml: Provides TOML format (data input) support for jinjanator
This plugin allows jinjanator to parse TOML data for processing in
templates. The format can be selected using --format toml or
autoselected by using a data file with a name ending with .toml.
Installation
pip install jinjanator-plugin-format-toml
Usage
Suppose you have an NGINX configuration file template, nginx.j2:
server {
listen 80;
server_name {{ nginx.hostname }};
root {{ nginx.webroot }};
index index.htm;
}
And you have a TOML file with the data, nginx.toml:
[nginx]
hostname="localhost"
webroot="/var/www/project"
This is how you render it into a working configuration file:
$ jinjanate nginx.j2 nginx.toml > nginx.conf
Options
This format does not support any options.
Release Information
Additions
- Added support for Python 3.15.
Changes
- Update to version 26.2.0 of jinjanator-plugins.
1 maintainer
Metadata
1 maintainer
Release files for jinjanator-plugin-format-toml 26.3.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 | |
|---|---|---|---|---|
| jinjanator_plugin_format_toml-26.3.0.tar.gz | 9.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jinjanator_plugin_format_toml-26.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.4 kB
Release files / jinjanator_plugin_format_toml-26.3.0.tar.gz
| Download URL | jinjanator_plugin_format_toml-26.3.0.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc5d25ea0d433563d11eb55b07af23b6cd26433eff5d9278d91c5b67c23f248e
|
|
BLAKE2b-256 checksum How to use checksums |
e10c24e9885aa2d3cbaa2a680accfe732ec0673b7480afdb32a18cce7cd2a6e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / jinjanator_plugin_format_toml-26.3.0-py3-none-any.whl
| Download URL | jinjanator_plugin_format_toml-26.3.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3fb9253402e5cfaf2f891955a1c9e599f4b23b8ea25b78838ee2860d3fa00f6f
|
|
BLAKE2b-256 checksum How to use checksums |
647b2d38cad9bec7fffefb18ed62a2744bc720736effcfac80bd5a0f000ed18c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logSecurity for jinjanator-plugin-format-toml 26.3.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for jinjanator_plugin_format_toml-26.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logA 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.
