Custom Context Processors executed twice

Hi, not sure if this has been an issue in the past but when I am using a custom context processor that is executed from TEMPLATE_CONTEXT_PROCESSORS, I get the issue where the context processor is being executed twice.

At first I thought it was an issue with the logging so I ignored it until I saw duplicate entries being written to the remote database so it seems it actually was executing the entire context processor for my app twice according to the logs.

This occurs when using render() in my views, since it already includes RequestContext(request) and all other context processors data is being executed from the settings declaration. If I use render_to_response() and omit the use of RequestContext(request) it does not execute twice.

I am able to continue using the render() return on the views with my custom context processors executing only one time by excluding 'debug_toolbar.panels.template.TemplateDebugPanel' from settings although this is not an actual fix

I thought I might bring this to some attention. I am using django-debug-toolbar-0.9.4 and Django 1.4.1

[mikelopez]

I am also having issues here

[aaugustin]

This could be related to #348 and #318.

[jezdez]

@whetstone Can you check with the recently released version 0.12 please?

[seddonym]

I'm also having this issue. I couldn't find version 0.12 but did just try with 0.11 and the issue is also there.

[aaugustin]

In Django 1.7, the output of all context processors is merged and added to the RequestContext as a single dict. See django/django@8d473b2.

As a consequence, it isn't possible to extract the output of individual template context processors from the template context anymore. That was already impossible in general because of the processors argument of RequestContext.

In order to extract the output of the context processors without calling them again, I'm afraid we have to monkey-patch RequestContext.