From 0b0741602b18928a418ba4661dc24b880daa5253 Mon Sep 17 00:00:00 2001
From: Zbigniew Siciarz <antyqjon@gmail.com>
Date: Sat, 18 May 2013 12:32:48 +0200
Subject: [PATCH] Fixed #20294 -- Documented context processors in
 TemplateResponseMixin.

---
 docs/ref/class-based-views/mixins-simple.txt | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/ref/class-based-views/mixins-simple.txt b/docs/ref/class-based-views/mixins-simple.txt
index 6796675529..377c85cc3b 100644
--- a/docs/ref/class-based-views/mixins-simple.txt
+++ b/docs/ref/class-based-views/mixins-simple.txt
@@ -60,6 +60,17 @@ TemplateResponseMixin
         altered later (e.g. in
         :ref:`template response middleware <template-response-middleware>`).
 
+        .. admonition:: Context processors
+
+            ``TemplateResponse`` uses :class:`~django.template.RequestContext`
+            which  means that callables defined in
+            :setting:`TEMPLATE_CONTEXT_PROCESSORS` may overwrite template
+            variables defined in your views. For example, if you subclass
+            :class:`DetailView <django.views.generic.detail.DetailView>` and
+            set ``context_object_name`` to ``user``, the
+            ``django.contrib.auth.context_processors.auth`` context processor
+            will happily overwrite your variable with current user.
+
         If you need custom template loading or custom context object
         instantiation, create a ``TemplateResponse`` subclass and assign it to
         ``response_class``.