Hi, since the unicode waves have calmed down, wouldn't it be a nice time to include the autoescaping patch?
I've brought most of the patches in ticket #2359 up to date. There are 3 patches, the first two deal with implementing autoescape as discussed and based on original ideas from Simon Willison, the third rewrites the admin interface to take use of it. It doesn't make sense to put work in the third patch since the admin rewrite isn't done, but the other patches could be applied independently. Actually, I think it would be a good idea to first put in the autoescaping, see if there are any issues overlooked, and only then make the admin interface use it. Auto-escaping is off by default, so there shouldn't be any compatibility issues at all. As you can see from the history, I use this patch for quite some time in production. Last comment from Malcolm (thanks for this great patch!), the patch author, asked Adrian for a review. http://code.djangoproject.com/ticket/2359 Cheers, Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9352-0 - Fax +49-911-9352-100 http://www.noris.de - The IT-Outsourcing Company Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk - Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
