Closed rossmiller closed 9 years ago
The jinja templates are slightly different from django so you can't just render django templates with jinja. Later, django-jinja works like middleware and intercepts by default by extension. If you keep your templates as is, with html file extension they are just ignored by django-jinja and rendered with the django templates engine.
Hi there,
We have been looking at the django-jinja project as a way of increasing the performance of template rendering within our project. We have set up multiple template back ends in order to try Jinja2 templates for a small percentage of the templates used within the site and bench mark their performance against the standard Django template system. We are having an issue where changes to the loaders option for the Django template setting is affecting the django-jinja loader setting.
The addition of the following (to turn off caching for local development) affects the django-jinja logic, in that, caching is also turned off for jinja2 templates.
This occurs whether or not the django-jinja template loader (shown below for clarity) is present in the configuration.