Hi Collin,
2014-11-05 3:21 GMT+01:00 Collin Anderson <[email protected]>:
> On Tuesday, 4 November 2014 17:30:27 UTC-5, Aymeric Augustin wrote:
>
I suspect the only reason why it isn't is to avoid changing the default
>> settings (django.conf.global_settings).
>>
> Right. Can we uncomment it anyway?
>
The problem with changing global_settings is that we don't have any way to
provide a deprecation path. However, since we have the checks framework,
we've started making such changes and attempting to warn users with checks.
Would you like to explore this direction?
I consider this idea to be independent from my refactoring.
Or, I would also be happy with a render('template.html', {'request':
> request, 'myvar': 3}) convention and then stop using context processors
> completely.
>
render(request, template_name, context) is such a strong convention at this
point that I prefer keeping it.
Of course, I expect many template engines to simply push the request into
the context and move on :-)
--
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/CANE-7mW3RMpBt%2BqtimNub6N1kWCkwHME4%3DRh3Utat2oQ5kaUcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
