id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux
7752,Context Processors get top of stack in RequestContext instances,teepark,nobody,"Currently, {{{RequestContext.__init__}}} applies context processors ''after'' updating from the provided dictionary. This should be the other way around because context processors are so general in scope (automatically applied to every {{{RequestContext}}} in the whole site).
{{{
d = {'anint': 7}
# this would get masked by any context processor that provides 'anint'
def myview(request):
return render_to_response(""home.html"", context_instance=RequestContext(request, d))
# so this form would be necessary
def myview(request):
rc = RequestContext(request)
rc.update(d)
return render_to_response(""home.html"", context_instance=rc)
}}}",,closed,Template system,master,,wontfix,,travis.parker@…,Design decision needed,0,0,0,0,,