Malcolm
I created the ticket (2743) and attached the patch.
Thanks,
Maritn
--~--~-~--~~~---~--~~
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@googlegr
On Mon, 2006-09-11 at 02:07 +, Martin wrote:
> Hi,
>
> I was wondering if there is a particular reason why the current value
> of a `named` cycle is not exported into the context so that it is
> accessable later in the tamplate as variable as well?
>
> Fore example:
>
> {% for obj in object
Hi,
I was wondering if there is a particular reason why the current value
of a `named` cycle is not exported into the context so that it is
accessable later in the tamplate as variable as well?
Fore example:
{% for obj in object_list %}
[]
{% if obj.need_second_row %}
[
