I'd be +1 on this, on the condition that there be some way to supress
errors, something like this.
{% for item in list %}
{{ item.title }}
{% silent %}
{{ item.owner }}
{% endsilent %}
{% endfor %}
On May 14, 11:03 pm, "John Lenton" <[EMAIL PROTECTED]> wrote:
> On Wed, May 14, 2008 at 7:19 PM, Christopher Allan Webber
>
> <[EMAIL PROTECTED]> wrote:
>
> > I'm just going to chime in here that a lot of our older apps at our
> > work use Zope Page Templates.
>
> > Largely we've found ZPT pages to be less pleaseant in all regards
> > *excepting* the fact that they never, ever silently fail. Just as
> > your code fails when there's a problem, so do your templates. It's
> > easy to see exactly where the problem is. In django, sometimes it can
> > be a total mystery. Sometimes you don't even know there's a problem
> > at all.
>
> > Thus I'm hugely +1 on this no-silent-failures bit, whether optional or
> > not.
>
> I'm very much on the +1 to no silent failures ever side, but one thing
> that makes it work in ZPT is the |nothing thingie, that allows you to
> explicitly ask for silence when needed.
>
> --
> John Lenton ([EMAIL PROTECTED]) -- Random fortune:
> The trouble with a lot of self-made men is that they worship their creator.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
