#24694: Add support for OPTIONS['context_processors'] to Jinja2 template backend
---------------------------------+------------------------------------
Reporter: carljm | Owner: nobody
Type: New feature | Status: new
Component: Template system | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by adamkerz):
I've just run into the same problem trying to use jinja2 and had a bit of
a look at middleware and the process_template_response method. From my
minor experimentation, it looks to me like that's at least roughly
equivalent to a context_processor - is there a reason that we can't get
rid of context_processors in favour of middleware? Seems like it will
support any template engine out of the box without having to modify the
template backend.
What are the differences between the two?
Also, doesn't django.utils.functional.lazy get around issues of loading it
whether it's used or not?
--
Ticket URL: <https://code.djangoproject.com/ticket/24694#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.8f03b072660e1948b197ed1499d2fc6e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
