[Solved]-How to use 3rd party app templatetags with Jinja 2?


According to coffin docs you will have to rewrite any custom django templates tags as custom Jinja2 extensions.

You could also use jinja2 macros feature to emulate the Django’s template tags. The most notable difference is that for Jinja2 macros it will be necessary to provide all the context data via the template context, while in Django tags you can access data using other ways (like loading from the database or calling other Python libraries).

I’ve been using Jinja2 templates for a while and never had a need to create a custom template tag.

It is possible to use django templates in one app on the site and jinja2 in another app, it is not a problem, but it is not readily possible to import or extend jinja2 templates from django templates and vs versa.



You can do this with coffin. Coffin supplies a way to register django-style tags to use within jinja2 templates:

from coffin import template
from ThrdPartyDjangoLib import djangoTagIWantToUse
register = template.Library()

register.tag('djangoTagIWantToUse', djangoTagIWantToUse)


Django’s structure does not allow for swapping the template engine since it is a core part of the system. Even if you can by using coffin, it is not a supported configuration and no third-party module can be expected to support it. It would be same as asking third party modules to support sqlalchemy because you found a way to make django work with it.

If you want to use jinja2, use a framework that is designed with a pluggable template engine – or one that comes without a template engine.

The integration page lists out of the box integrations that come with Jinja2. On that page you can see that Pyramid is supported – and that is because by design pyramid allows for pluggable components.

Flask (made by the same people behind Jinja2) has native support for Jinja2.

Leave a comment