On Sat, Apr 26, 2008 at 9:38 PM, Darryl Ross <[EMAIL PROTECTED]> wrote:So my question is, is there an argument which will disable auto-escaping?
Nevermind me, the version of code I was reading on my dev machine through was older than I thought, pre-autoescaping. I did an update and there is now an optional argument to the Context() constructor which does what I want.
No, it isn't obvious. Somebody writing a template should know exactly how it is going to be parsed. That person isn't necessarily the person writing the view (code). To keep the designer/developer separation clean, we made auto-escaping controllable via the template.
Which is all well and good for a "website" designer. Someone who is writing templates for emails might not be expecting HTML escaping, but anyway.
You are bringing up points that were hashed out again and again on the developers list leading up to autoescaping being committed. Yes, there are differing opinions. There's no way to reach unanimous consensus here and we picked one, quite usable, method for the implementation.
Sorry, my searching in google hadn't turned up any archives of any conversations like that.
By the way, I'm not against the auto-escaping, I just think there are situations (such as generation of email messages) where it is not required. I'm glad that the option to turn it off is actually there.
Thanks for your hard work guys, it is appreciated. Part of my reason for going through this is to try to get some better idea of the codebase so I can contribute a bit more.
Cheers Darryl
signature.asc
Description: OpenPGP digital signature
