On 8/1/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > Is autoescaping being on *really* that big a deal to you? How many > places do your variables actually contain HTML? And if the answer is > "many", then is it really all that big a deal to make a one-time > modification to your base templates? >
Hi, Jacob. May I ask a clarifying question here? Is autoescaping going to be on by default, or no? And what exactly is it that's being added here -- a template tag for turning on/off autoescaping? I know we've gone round and round about this, so I don't mean to cover old ground, but I did search the archives and wiki a bit and I'm still not clear. If it's not on by default, as James said, how does this make life safer for anyone? Don't get me wrong, I've argued against autoescaping before, but if it's in the framework why not turn it on by default? And I guess I don't really see the difference in turning on/off autoescaping globally in a base template vs. a global setting. Cheers, deryck --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
