Skip to main content

Unobtrusive jinja2 integration in Django

Project description

© 2014 Thomas Khyn

Unobtrusive jinja2 integration in Django

Freely inspired from django-jinja and django-jinja2, as none of them met all my expectations!


  • Install djinga using the method of your choice

  • Add ‘djinga’ to your INSTALLED_APPS

  • Change the TEMPLATE_LOADERS settings to:

  • Add the relevant settings for jinja2

How it works

By default, a template will be rendered using Django’s built-in template engine if it has a .html, .htm, .djhtml or .djhtm file extension. If it has a .jjhtml or .jjhtm file extension, it will be rendered by Jinja2, using the setting values provided in django’s setting module.



The file extensions for templates that should be rendered with Django’s internal template engine.

Defaults to ('html', 'htm', 'jjhtml', 'jjhtm')


The file extensions for templates that should be rendered with Jinja2.

Defaults to ('jjhtml', 'jjhtm')

A function taking as sole argument the path of the template file and returning True if the file should be rendered with Jinja2. Defaults to a function returning True if the extension is in JINJA2_JJ_EXTS
The extensions to be loaded by jinja2. Some extensions are shipped with djinga under djinga.ext.*
The jinja2 environment’s constructor keyword arguments as a dictionary.
The jinja2 globals as a dictionary.
The jinja2 filters as a dictionary.

Extensions and template tags

Built-in Jinja2 extensions

Djinga comes with several Jinja2 extensions

Provides a {% static 'path' %} tag to refer to Django’s staticfiles directory
Provides a {% css 'rel/path/to/file.css' %} tag that generates a HTML link element refering to the css file located at a relative path in a css directory. The css directory’s path can be defined relatively to Django’s staticfiles directory through the setting JINJA2_STATIC_CSS
Same as djinga.ext.css but generates a HTML script element refering to a javascript file. The js directory’s relative path can be set through the setting JINJA2_STATIC_JS
Simply concatenates django’s MEDIA_URL to the argument provided
Provides a {% django %}{% enddjango %} tag to include django template language in a jinja2 template. For this tag to work, the django.core.context_processors.request context processor must be enabled.
Provides a tag for URL reversing, similar to the django templates one.

Other Jinja2 extensions

djinga.ext.htmlcompress.HTMLCompress / SelectiveHTMLCompress
© 2011 Armin Ronacher. Eliminates useless whitespace at template compilation time without extra overhead.

Django template tags

The following tags are available in any django template explicitly loading djinga_tags using the {% load djinga_tags %} statement.

Overrides the standard {% extends %} tag and enables it to refer to jinja2 files as well as normal django template files. While the template engine for the current file remains Django’s one, the template engine for the extended file can be either Jinja2 or Django, depending on the file extension (in JINJA2_DJ_EXTS or JINJA2_JJ_EXTS)

Management command

Djinga overrides the Django core management command makemessages to include the specific Jinja2 translation tags and ensure the strings marked for translation in Jinja2 templates appear in the translations dictionary.

Project details

Download files

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

Files for djinga, version 1.1
Filename, size File type Python version Upload date Hashes
Filename, size djinga-1.1-py2.7.egg (33.1 kB) File type Egg Python version 2.7 Upload date Hashes View
Filename, size (19.6 kB) File type Source Python version None Upload date Hashes View

Supported by

Pingdom Pingdom Monitoring Google Google Object Storage and Download Analytics Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page