Pyramid-jinja2

==================

- 91: Fix a recursion error while attempting to include a template with the
same name as one of the parents that was already loaded. [mmerickel]

==================

- Fix 2.3.1 brownbag release. It had some erroneous didn't-mean-to-push
changes that are now solved. Brought coverage back up to 100%.

==================

- Improve the template-relative searchpath logic to search more possibilities
in the include-chain built up from templates including or extending
other templates. The logic for when the chain was longer than just one
template including another template was broken.

================

- Require ``pyramid_jinja2`` to be included even when using
``pyramid_jinja2.renderer_factory``. It is now a thin wrapper around the
default renderer and can be used to share the same settings with another
file extension. [mmerickel]

Backward Incompatible Changes
-----------------------------

- ``pyramid_jinja2`` **must** be included into the ``Configurator`` in order
to use ``pyramid_jinja2.renderer_factory`` otherwise you may see the
exception::

ValueError: As of pyramid_jinja2 2.3, the use of the
"pyramid_jinja2.renderer_factory" requires that pyramid_jinja2 be
configured via config.include("pyramid_jinja2") or the equivalent
"pyramid.includes" setting.

The fix is to include ``pyramid_jinja2``::

config.include("pyramid_jinja2")

================

- 88: Formalize template loading order and allow all lookups to fallback to
the search path. A template is now always searched for relative to its
parent template. If not found, the lookup will fallback to the search path.
[mmerickel]

- Add ``prepend`` option to ``config.add_jinja2_search_path`` to allow
prepending of paths to the beginning of the search path if a path should
override previously defined paths. [mmerickel]

================

- The 2.0 series started adding the package that invoked
``config.add_jinja2_renderer`` to the template search path. This is
being removed in favor of explicit search paths and will hopefully not
affect many people as it has only been available for a couple weeks. The
only automatic search path left is the one added by the default ``.jinja2``
renderer created when including ``pyramid_jinja2``. [mmerickel]

- Adjust the ``config.include("pyramid_jinja2")`` to add any packages from
``jinja2.directories`` **before** the default search path at the base of
the app. Previously there was no way to override that search path.
[mmerickel]