#7752: Context Processors get top of stack in RequestContext instances
---------------------------------------------+------------------------------
Reporter: teepark | Owner: nobody
Status: new | Milestone:
Component: Template system | Version: SVN
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by mtredinnick):
* needs_better_patch: => 0
* stage: Unreviewed => Design decision needed
* needs_tests: => 0
* needs_docs: => 0
Comment:
This would have to be pre-1.0 if we do it, since it's backwards
incompatible in a visible way. Could go either way, though. The idea is
that context processors are orthogonal to the rest of the code and if you
accidentally reuse a context processor variable, accidentally overwriting
the context processor-intended result may not a good result. Of course,
some people will want to be to able to replace them on a per-view basis,
which may or may not be against the spirit of context processors.
For those reasons, moving to design decision needed. It needs thought.
--
Ticket URL: <http://code.djangoproject.com/ticket/7752#comment:1>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
