On 10/01/15 22:40, Collin Anderson wrote:
Hi All,
In talking to Aymeric and other developers, we're starting to think
about the usefulness of global template context_processors. It seems to
us that ideally you should only need the "request" context processor.
You could even imagine removing context_processors all together and
having render() and class based views simply put the request in the context.
FWIW, I habitually replace the multiple default context_processors with
a single custom processor which does the same thing. Then I add and
remove context items in a single place as the project goes on. The same
with third-party context_processors (they tend to be straightforward).
Backwards compatability aside, is a list of functions better than a
single function?
--
You received this message because you are subscribed to the Google Groups "Django
developers (Contributions to Django itself)" 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].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/m8vkbj%24e1j%241%40ger.gmane.org.
For more options, visit https://groups.google.com/d/optout.
