On Tue, Feb 22, 2011 at 6:41 AM, Chris Beaven wrote:
> After hunting down a very elusive bug, I found the cause to be due to the
> fact that render_to_string leaves the context in a different state than it
> started (due to the context stack being pushed before rendering, and then
> not popped).
>
After hunting down a very elusive bug, I found the cause to be due to the
fact that render_to_string leaves the context in a different state than it
started (due to the context stack being pushed before rendering, and then
not popped).
This behavior differs from a standard Template.render call
