sphinx-jinja-variants
Render Sphinx compositions with temporary Jinja bindings and a prepared RST source.
$ pip install sphinx-jinja-variantsUse render_source_variant from a custom Sphinx directive. It inherits the selected context’s existing values, prepares the source once for standard include-section directives, runs your rendering callback, and restores the original bindings. Your code chooses variants, content preparation, validation, and presentation.
See the Python API and the platform example. To contribute, see the contributor guide.
1 maintainer
Metadata
1 maintainer
Release files for sphinx-jinja-variants 2026.11.2.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 | Actions |
|---|---|---|---|---|
| sphinx_jinja_variants-2026.11.2.1.tar.gz | 151.7 kB | With provenance | Details for sphinx_jinja_variants-2026.11.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sphinx_jinja_variants-2026.11.2.1-py3-none-any.whl | Python 3 | none | any | Details for sphinx_jinja_variants-2026.11.2.1-py3-none-any.whl |
Total release size: 156.2 kB
Release files / sphinx_jinja_variants-2026.11.2.1.tar.gz
| Download URL | sphinx_jinja_variants-2026.11.2.1.tar.gz |
|---|---|
| Size | 151.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a3dc7a3cb0074b8922b6da908a74d0ccdbc07a0c1928ce81b10d694210c7ebf
|
|
BLAKE2b-256 checksum How to use checksums |
3e483691134f69cf5fa3498743fc36ad45a02d5e24d084d44a85867ff2c3e27e
|
| 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 2, 2026.
Transparency logRelease files / sphinx_jinja_variants-2026.11.2.1-py3-none-any.whl
| Download URL | sphinx_jinja_variants-2026.11.2.1-py3-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
63ca7a2dd6174d1cfb41d7b21674118a8e062f7bed5e5ff4fe060b89241af083
|
|
BLAKE2b-256 checksum How to use checksums |
8357b1d85444563742483d1b48335402309f2bf9ec2f8538caadaf9bd2f3941f
|
| 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 2, 2026.
Transparency logSecurity for sphinx-jinja-variants 2026.11.2.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for sphinx_jinja_variants-2026.11.2.1.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 2, 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.
