Sphinx-jinja

Latest version: v2.0.2

Safety actively analyzes 681775 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

2.0.2

-----

Release the dependency to >4.2 to be more compatible as a deep dependency

2.0.1

-----

Readme fix

2.0.0

-----

Release the docutil dependency constraint to allow more recent version.

**Breaking change**: In order to be compatible with modern sphinx, the plugin is now in its own
module, and not anymore in the "sphinxcontrib" namespace.

You will need to change you conf.py with the following pseudo patch:


- extensions = ['sphinxcontrib.jinja']
+ extensions = ['sphinx_jinja']

1.4.0

-----

Implement the header_update_levels flag, which allows jinja blocks to use the same header (titles) level as the parent block.

1.3.0

-----

Use app.srcdir as jinja_base.

This affects people that include files from jinja context and use separate
source and build directories. They should change:


.. jinja::
:file: source/test.rst


to


.. jinja::
:file: test.rst


* Add `header_update_levels` option to let headers behave in the same way as
if include via the `include` directive.

1.2.1

-----
untight the dependency on jinja2 from ^2.11 to >=2.11

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.