Patches Jinja2 v3 to restore compatibility with earlier Sphinx versions.
Also makes some Sphinx versions work correctly on Python 3.10.
The patches can be disabled by setting the environment variable NO_SPHINX_JINJA2_COMPAT to 1. (v0.2.0 and newer only)
Tests |
|
|---|---|
PyPI |
|
Anaconda |
|
Activity |
|
QA |
|
Other |
Installation
sphinx-jinja2-compat can be installed from PyPI or Anaconda.
To install with pip:
$ python -m pip install sphinx-jinja2-compat
To install with conda:
First add the required channels
$ conda config --add channels https://conda.anaconda.org/conda-forge $ conda config --add channels https://conda.anaconda.org/domdfcoding
Then install
$ conda install sphinx-jinja2-compat
Metadata
Release files for sphinx-jinja2-compat 0.4.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 | |
|---|---|---|---|---|
| sphinx_jinja2_compat-0.4.1.tar.gz | 5.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sphinx_jinja2_compat-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.3 kB
Release files / sphinx_jinja2_compat-0.4.1.tar.gz
| Download URL | sphinx_jinja2_compat-0.4.1.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0188f0802d42c3da72997533b55a00815659a78d3f81d4b4747b1fb15a5728e6
|
|
BLAKE2b-256 checksum How to use checksums |
439843313781f29e8c6c46fec907430310172d6f207e95e4fbea9289990fbbfe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Release files / sphinx_jinja2_compat-0.4.1-py3-none-any.whl
| Download URL | sphinx_jinja2_compat-0.4.1-py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
64ca0d46f0d8029fbe69ea612793a55e6ef0113e1bba4a85d402158c09f17a14
|
|
BLAKE2b-256 checksum How to use checksums |
cec84fd58c1000d7f8f5572c507f4550d2e2d9741e500c68eb2e3da17cbe5a85
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Security for sphinx-jinja2-compat 0.4.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.