Re: Using Django with Jinja2 and TEMPLATE_DEBUG=True

On Thursday 07 January 2010 01:35:50 Russell Keith-Magee wrote: > From a cursory inspection, I'm not sure there is much we can do with > (1) - there isn't a lot of detail on Exception that can be used for a > capability check, and the only attribute that is actually needed is > 'source' (albeit in

Re: Using Django with Jinja2 and TEMPLATE_DEBUG=True

> No, it wouldn't (at least, not completely). Jinja wouldn't extend > Django's TemplateSyntaxError class, so using the approach you > describe, Jinja's TemplateSyntaxErrors wouldn't break the debug page, > but you wouldn't get good template error feedback either. FWIW, I don't think that's an

Re: Using Django with Jinja2 and TEMPLATE_DEBUG=True

On Thu, Jan 7, 2010 at 2:54 AM, Rick van Hattem wrote: > Hi, > > Maybe this question has already been asked, but I am wondering why Jinja2 > compatibility can't be fixed in a clean way. Currently the code assumes that > if an exception has a "source" attribute that it's a

Using Django with Jinja2 and TEMPLATE_DEBUG=True

Hi, Maybe this question has already been asked, but I am wondering why Jinja2 compatibility can't be fixed in a clean way. Currently the code assumes that if an exception has a "source" attribute that it's a Django exception and can be processed as such. (the code: