#25839: RequestContext does not apply context processors [regression]
-------------------------------------+-------------------------------------
     Reporter:  direx                |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Documentation        |                  Version:  1.8
     Severity:  Normal               |               Resolution:
     Keywords:  RequestContext,      |             Triage Stage:  Accepted
  regression                         |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by direx):

 Replying to [comment:6 aaugustin]:
 > (In case that's not clear enough, saying "you are making this a little
 too easy for you" to a person who works in their free time guarantees
 their non-cooperation. My involvement with this issue stops here.)

 I don't get your point. I was neither rude, nor was my comment meant to be
 offensive. I am also reporting bugs in my free time, hoping to help other
 users who might stumble upon the same issue. Sorry if you got me wrong
 there.

 Replying to [comment:7 carljm]:
 > So I think this ticket should be fixed the same way we'd have fixed it
 if we'd noticed it before the release of 1.8: by making a note of the
 issue in the backwards-incompatible changes section of the 1.8 release
 notes, and perhaps also clarifying the RequestContext docs to note that
 values from context processors are only available in a RequestContext once
 it has been bound to a template (which Django does automatically when you
 render a template using a RequestContext).

 To me this entire issue is actually not a biggie. Some third-party apps I
 am using rely on that behavior, but I can fix that. So I'd agree with you
 here that adding it to the list of backwards-incompatible changes and
 maybe a small note in the docs would probably be sufficient.

--
Ticket URL: <https://code.djangoproject.com/ticket/25839#comment:8>
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 
https://groups.google.com/d/msgid/django-updates/063.7af5210955852b45f8ee787c49afe77b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to