On 27 Jul 2006, at 21:01, Tom Tobin wrote: > From what I recall of conversations on the subject, default behavior > will not be changed to auto-escape. Auto-escaping, under whatever > proposal is accepted, will require some form of action to enable.
I like to think that's not set in stone yet. There's a lot of opposition to having it on by default, but I'm hoping there's a chance that people might start to change their minds once they've had the opportunity to try it out. I'm not going to push the point until it's ready to try though, and I think that arguing the point is pointless without running code to act as an example. (Malcolm Tredinnick's patch looks like a really great bash at this; it's great that someone's taking the initiative and hammering out some code). Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
