Hi Anssi, On 17 oct. 2014, at 14:49, Anssi Kääriäinen <[email protected]> wrote:
> The FAQ section says that template context processors isn't going to be > supported for context processors. Indeed, at this time, my theoretical position is not to enforce such an API and leave it up to template engines. But I may settle for a pragmatic position if this results in every template engine copy-pasting 50 lines of code to provide that feature. As shown by the `render` shortcut, APIs in this area must be pragmatic, even if that requires some compromise with the general design. > The context processors return a dictionary to be added to the context, > so there is nothing template language specific in this definition. It's implemented in RequestContext which used to be called DjangoContext until magic-removal (2006) and lives in django.template.context. That's why I considered it part of the Django template language itself. > What is the rationale of dropping context processors out of the > proposal? It seems supplying different template engines with different > data isn't going to work well for any project in which one wants to > replace DTL templates. Yes, providing all templates with a common set of request-specific values is a useful feature. It was on my todo list :-) -- Aymeric. -- 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/18EED14B-40E2-4107-9C72-EDB0C47C800F%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
