On Monday, September 15, 2014 3:24:19 PM UTC+2, germano guerrini wrote: > > I'd like to bump this. While there might be better solutions, I think the > issue is not so wacky after all. >
To be honest, I don't see an issue here at all. What the view returns should end up in the template. If tags/whatever in your template override variables at will that's a bug in your application imo. Also your code example fails to show where the key is overridden -- ie an include wouldn't override cause the stack is popped after the include. Do you have a concrete example causing this "issue"? Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d7df11c7-4a66-44fd-af98-4367e9322f3f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
