Ticket #13841: 13841-docs.diff

ref/templates/api.txt

@@ -516 +516 @@
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 A context processor has a very simple interface: It's just a Python function
-that takes one argument, an :class:`~django.http.HttpRequest` object, and
-returns a dictionary that gets added to the template context. Each context
-processor *must* return a dictionary.
+that takes at least one argument, an :class:`~django.http.HttpRequest` object.
 
+.. versionadded:: 1.2
+   The optional keyword argument ``context`` is now supported, which allows 
+   access to the current :class:`~django.template.Context` object.
+
+The function returns a dictionary that gets added to the template context. 
+Each context processor *must* return a dictionary.
+
 Custom context processors can live anywhere in your code base. All Django cares
 about is that your custom context processors are pointed-to by your
 :setting:`TEMPLATE_CONTEXT_PROCESSORS` setting.