Skip to main content

An adapter for using Jinja2 templates with Django.

Project description

.. _jingo:
.. module:: jingo


.. note:: This document may be out of date. The up-to-date documentation can
be found on `Read the Docs <>`_.

Jingo is an adapter for using Jinja2_ templates within Django.

.. note:: Coffin or Jingo?

Jingo differs from Coffin_ in two major ways:

* Jingo serves purely as a minimalistic bridge between Django and Jinja2_.
Coffin_ attempts to reduce the differences between Jinja2_ templates
and Django's native templates.

* Jingo has a far superior name, as it is a portmanteau of 'Jinja' and

.. _Coffin:
.. _Jinja2:

.. _usage:


When configured properly (see Settings_ below) you can render Jinja2_ templates in
your view the same way you'd render Django templates::

from django.shortcuts import render

def my_view(request):
context = dict(user_ids=(1, 2, 3, 4))
return render(request, 'users/search.html', context)

.. note::

Not only does ``django.shorcuts.render`` work, but so does any method that
Django provides to render templates.

.. _settings:


You'll want to use Django to use jingo's template loader.
In ````::


This will let you use ``django.shortcuts.render`` or

You can optionally specify which filename patterns to consider Jinja2 templates::

JINGO_INCLUDE_PATTERN = r'\.jinja2' # use any regular expression here

This will consider every template file that contains the substring `.jinja2` to
be a Jinja2 file (unless it's in a module explicitly excluded, see below).

And finally you may have apps that do not use Jinja2, these must be excluded
from the loader::

JINGO_EXCLUDE_APPS = ('debug_toolbar',)

If a template path begins with ``debug_toolbar``, the Jinja loader will raise a
``TemplateDoesNotExist`` exception. This causes Django to move onto the next
loader in ``TEMPLATE_LOADERS`` to find a template - in this case,

.. note::
Technically, we're looking at the template path, not the app. Often these are
the same, but in some cases, like 'registration' in the default setting--which
is an admin template--they are not.

The default is in ``jingo.EXCLUDE_APPS``::


.. versionchanged:: 0.6.2
Added ``context_processors`` application.

If you want to configure the Jinja environment, use ``JINJA_CONFIG`` in
````. It can be a dict or a function that returns a dict. ::

JINJA_CONFIG = {'autoescape': False}

or ::

return {'the_answer': 41 + 1}

Template Helpers

Instead of template tags, Jinja encourages you to add functions and filters to
the templating environment. In ``jingo``, we call these helpers. When the
Jinja environment is initialized, ``jingo`` will try to open a ````
file from every app in ``INSTALLED_APPS``. Two decorators are provided to ease
the environment extension:

.. function:: jingo.register.filter

Adds the decorated function to Jinja's filter library.

.. function:: jingo.register.function

Adds the decorated function to Jinja's global namespace.

.. highlight:: jinja

Default Helpers

Helpers are available in all templates automatically, without any extra

.. automodule:: jingo.helpers

Template Environment

A single Jinja ``Environment`` is created for use in all templates. This is
available as ``jingo.env`` if you need to work with the ``Environment``.


Since we all love L10n, let's see what it looks like in Jinja templates::

<h2>{{ _('Reviews for {0}')|f( }}</h2>

The simple way is to use the familiar underscore and string within a ``{{ }}``
moustache block. ``f`` is an interpolation filter documented below. Sphinx
could create a link if I knew how to do that.

The other method uses Jinja's ``trans`` tag::

{% trans user=review.user|user_link, date=review.created|datetime %}
by {{ user }} on {{ date }}
{% endtrans %}

``trans`` is nice when you have a lot of text or want to inject some variables
directly. Both methods are useful, pick the one that makes you happy.


Django marks its form HTML "safe" according to its own rules, which Jinja2 does
not recognize.

This monkeypatches Django to support the ``__html__`` protocol used in Jinja2
templates. ``Form``, ``BoundField``, ``ErrorList``, and other form objects that
render HTML through their ``__unicode__`` method are extended with ``__html__``
so they can be rendered in Jinja2 templates without adding ``|safe``.

Call the ``patch()`` function to execute the patch. It must be called
before ``django.forms`` is imported for the conditional_escape patch to work
properly. The root URLconf is the recommended location for calling ``patch()``.


import jingo.monkey


To run the test suite, you need to define ``DJANGO_SETTINGS_MODULE`` first::

$ export DJANGO_SETTINGS_MODULE="fake_settings"
$ nosetests

or simply run::

$ python

To test on all supported versions of Python and Django::

$ pip install tox
$ tox

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

jingo-0.8.tar.gz (10.4 kB view hashes)

Uploaded Source

Built Distribution

jingo-0.8-py2.py3-none-any.whl (13.2 kB view hashes)

Uploaded Python 2 Python 3

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page