I note from the release notes for Django 1.8 https://docs.djangoproject.com/en/1.8/releases/1.8/ the remark under the section: "dictionary and context_instance arguments of rendering functions" (which includes django.shortcuts.render_to_response())
"If you’re passing a Context <https://docs.djangoproject.com/en/1.8/ref/templates/api/#django.template.Context> in context_instance, pass a dict <https://docs.python.org/3/library/stdtypes.html#dict> in the context parameter instead. If you’re passing a RequestContext <https://docs.djangoproject.com/en/1.8/ref/templates/api/#django.template.RequestContext>, pass the request separately in the *request *parameter." However, render_to_response* does not have a request parameter*. Is that an omission? I use the following idiom quite a lot: response = render_to_response('some_template.html', {'foo': 'bar'}, RequestContext(request)) If the passing of a context_instance is now to be avoided, I would expect to be able pass in the request object directly to render_to_response. Otherwise how are the context processors to do their job? -- Stephen -- 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/e9b54373-9901-4a5a-8101-89b6a7cedaf6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
