From c274a9cbd03bd3a90c2400b6efc63a59c5e64b33 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 31 Aug 2012 20:24:33 -0400 Subject: [PATCH] [1.4.X] Fixed #18642 - Added a note suggesting the use of render() rather than render_to_response() if you need RequestContext in your template. Backport of f99ecaff06 from master --- docs/ref/templates/api.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/ref/templates/api.txt b/docs/ref/templates/api.txt index 47f7540191..1955bd4ead 100644 --- a/docs/ref/templates/api.txt +++ b/docs/ref/templates/api.txt @@ -419,6 +419,10 @@ optional, third positional argument, ``processors``. In this example, the my_data_dictionary, context_instance=RequestContext(request)) + Alternatively, use the :meth:`~django.shortcuts.render()` shortcut which is + the same as a call to :func:`~django.shortcuts.render_to_response()` with a + context_instance argument that forces the use of a ``RequestContext``. + Here's what each of the default processors does: django.contrib.auth.context_processors.auth