Malcolm Tredinnick: > I didn't change django.utils.html.escape() though, since I was trying to > avoid breaking existing code and that function can be called from > outside the templating system (in that sense, the naming is logical; > away from the templating system, escape() escapes always). The way it's > currently implemented, the auto-escaping additions are transparent and > fully backwards-compatible. If we change django.utils.html.escape() that > is no longer true, but we should make a decision about that before > applying the patch to the mainline.
OK, I'm +0 for keeping django.utils.html.escape() as is. But when you use auto-escaping, you should probably never use escape() directly, and this is a point for the documentation. So long, 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 --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
