On 8/4/07, Tom Tobin <[EMAIL PROTECTED]> wrote:
> On 8/4/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> >
> > On 8/1/07, James Bennett <[EMAIL PROTECTED]> wrote:
> > > Let's just do:
> > >
> > > 1. Autoescape on by default.
> > > 2. Autoescape is turned off by the {% autoescape off %}
> > > 3. Autoescape happens irregardless of what the template's source file
> > > or source string happened to be named.
> >
> > I'm +1 on this approach. Let's just do it.
>
> Do you have any particular issues with Simon's modification of my
> proposal (turning autoescaping off by default only for a whitelist of
> extensions such as .txt)? If I'm going to go ahead and whip up some
> code, I'd like there to be *some* chance in hell of it getting
> accepted. ^_^
Or hell, maybe I'm looking at this the wrong way.
A lot of my angst here comes from the collision between my desire for
Django's template system to serve as a good *general-purpose*
templating system for everything from HTML to LaTeX to what-have-you,
and Django's (obviously) web-centric standpoint. There's been quite a
bit of talk over time regarding splitting Django's template system out
into a separate library; maybe it's time to do that. It would make
perfect sense for the *library* to take a setting for defaulting
autoescaping to on or off depending on a developer's needs in various
contexts, while still keeping autoescaping on by default for Django's
use of the library.
Thoughts?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
