Within a Django template, sometimes I find myself wishing that I had access to the loop item from the previous iteration of a loop.
Usually the ifchanged tag is good enough for my purposes, but occasionally if some attribute of the loop item has changed I need to do further examination of the previous item to determine what sort of wrap-up (e.g., tag closing) needs to be done. I'm considering adding a forloop.previous (or somesuch) variable to the supplemental variables produced by the for tag. If forloop.first is true, this value would always be None, but otherwise it would reference the actual loop item from the prior iteration. Is there sufficient interest in this that I should consider going the extra mile by opening a ticket and submitting a patch? Or (please excuse my ignorance!) is opening a ticket actually the preferred way to gauge the interest level? -- Scott -- http://scott.andstuff.org/ | http://truthadorned.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
