#27258: Context processors are not called when using RequestContext and Django
     Reporter:  Andi Albrecht    |                    Owner:  nobody
         Type:  Bug              |                   Status:  new
    Component:  Template system  |                  Version:  1.10
     Severity:  Normal           |               Resolution:
     Keywords:                   |             Triage Stage:  Unreviewed
    Has patch:  0                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  0
Easy pickings:  0                |                    UI/UX:  0

Comment (by Andi Albrecht):

 Replying to [comment:1 Tim Graham]:
 > I didn't look into the details but the conversation in #25839 might be

 Both issues are related. To me #25839 describes the fact, that the
 (global) `TEMPLATE_CONTEXT_PROCESSORS` couldn't be used. Here I describe a
 scenario where no context_processor are called even when properly
 configured or when explicitely given in the constructor of

 There's an example in the Django docs about using RequestContext:
 requestcontext (the one with the `ip_address_processor`).
 Just change `template = Template('{ title }}: {{ ip_address }}')` to
 `template = loader.get_template('my_template.html')` and it doesn't work
 anymore, since `django.template.backends.django.Template` behaves
 different than `django.template.Template`.

Ticket URL: <https://code.djangoproject.com/ticket/27258#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to