sphinx-jinja2
A sphinx extension to add the
jinjadirective, for rendering Jinja templates (powered by minijinja).
Note: This is an adaption of https://github.com/tardyp/sphinx-jinja, which appears to be unmaintained.
See also: sphinx-ub-directives. The ub-template directive in
sphinx-ub-directives renders minijinja templates with the same
:file:, :ctx:, :debug: and :raw: options; with its configuration in ubproject.toml, the same project also renders in ubCode.
It is stricter by design: contexts are data only (no env, Python objects or functions),
there are no custom filters, tests or environment options, and template output may not contain headings.
The two extensions can be used side by side. sphinx-jinja2 remains maintained with bug fixes and compatibility updates,
while new template features are developed in sphinx-ub-directives, which is developed alongside sphinx-needs and also works in ubCode;
to switch, see Migrating from sphinx-jinja2.
See the documentation for more information.
Metadata
Release files for sphinx-jinja2 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 | Actions |
|---|---|---|---|---|
| sphinx_jinja2-0.1.0.tar.gz | 9.9 kB | With provenance | Details for sphinx_jinja2-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sphinx_jinja2-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for sphinx_jinja2-0.1.0-py3-none-any.whl |
Total release size: 20.1 kB
Release files / sphinx_jinja2-0.1.0.tar.gz
| Download URL | sphinx_jinja2-0.1.0.tar.gz |
|---|---|
| Size | 9.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed470d76bf1a4cc47ffb57a89798dd631519ac97bddec2ba5b4934bf0c1bc7e9
|
|
BLAKE2b-256 checksum How to use checksums |
d06d39d292acd00d10879676a6e1a013342b00dc7c258d34eb88f2b637287dcf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logRelease files / sphinx_jinja2-0.1.0-py3-none-any.whl
| Download URL | sphinx_jinja2-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
deba808a95c5329a82a655d84ff47d284967d8fcccd0c2d8011d99c67c63cbd8
|
|
BLAKE2b-256 checksum How to use checksums |
208e4cc82a7b84c7eb01cfcdf6a38bf45ce7d4c9371b6dd430d49b5ede0151ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 10, 2026.
Transparency logSecurity for sphinx-jinja2 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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for sphinx_jinja2-0.1.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 Nov 10, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.