On Mon, Jun 3, 2013 at 1:20 PM, Shai Berger <[email protected]> wrote:
> On Monday 03 June 2013, Russell Keith-Magee wrote:
> > Alternatively, add new sub tags to {% for %}:
> >
> > {% for bee in my_bonnet.bees %}
> > {% pre %}
> > <ul class='bee list'>
> > {% body %}
> > <li>{{ bee }}<li>
> > {% post %}
> > </ul>
> > {% empty %}
> > <span>No bees in your bonnet.</span>
> > {% endfor %}
> >
> > but that's starting to get verbose, and leaves ambiguous what to do with
> > content appearing between the opening {% for %} and the {% pre %}
> >
> It's also sort of available already:
>
> I'm fully aware that it's *possible* to handle already. The point is that
it's such a common use case that is should be easy to render without
requiring an extra 4 lines of obscure template logic, an extra 2 levels of
indentation, or an expensive double calculation.
Yours,
Russ Magee %-)
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
