Hi, I found myself needing to reference the previous or next element
of a list within a for loop of a template.
I think it would be pretty easy to implement the following extra
members to the forloop context variable:
+ forloop.next_element
+ forloop.next_counter
+ forloop.next_counter0
+ for
Santiago Perez wrote:
> Hi, I found myself needing to reference the previous or next
> element of a list within a for loop of a template. I think it
> would be pretty easy to implement the following extra members
> to the forloop context variable:
>
> + forloop.next_element
> + forloop.next_coun
Hi Everyone,
I read a couple weeks ago about an app that has been pre-configured
with a bunch of the necassary components (authentication,
registration, etc), but can't for the life of me find it/remember what
it was...
does anyone recall?
Thank you,
Michael
--~--~-~--~~---
On Mon, Jan 26, 2009 at 3:51 PM, Michael Trosen wrote:
>
> Hi Everyone,
>
> I read a couple weeks ago about an app that has been pre-configured
> with a bunch of the necassary components (authentication,
> registration, etc), but can't for the life of me find it/remember what
> it was...
>
> does
yes, you are correct on both aspects, thanks, and sorry :)
Michael
On Jan 26, 3:57 pm, Alex Gaynor wrote:
> On Mon, Jan 26, 2009 at 3:51 PM, Michael Trosen
> wrote:
>
>
>
> > Hi Everyone,
>
> > I read a couple weeks ago about an app that has been pre-configured
> > with a bunch of the necassar
I have also needed this in the past and just hacked the forloop code
to provide the variables. I can make a patch available with a couple
of tests if there is interest in including this.
On Mon, Jan 26, 2009 at 2:55 PM, Tim Chase
wrote:
>
> Santiago Perez wrote:
>> Hi, I found myself needing to
On Mon, 2009-01-26 at 16:16 -0200, Santiago Perez wrote:
> Hi, I found myself needing to reference the previous or next element
> of a list within a for loop of a template.
> I think it would be pretty easy to implement the following extra
> members to the forloop context variable:
>
> + forloop
On Sat, 2009-01-24 at 08:27 -0800, nside wrote:
> Sorry about that.
> Do you think such a library, once stable, could make it to the trunk?
We never predict the future. It's not impossible, but that's because
nothing is. Whether it's actually a common pattern with either a
significant barrier to
On Sun, 2009-01-25 at 09:51 -0800, PB wrote:
> Hi,
>
> I've been experimenting with model inheritance and have become pretty
> dissatisfied with the way it is implemented in Django. It seems that
> this part of the ORM has not received as much TLC and thought as the
> rest of the framework.
Slig
On Sat, 2009-01-24 at 14:13 -0800, mrts wrote:
> After several discussions with Honza, we are still on somewhat
> different positions what the validator function signature should
> be and how core validators should access the fields of a form or
> a model instance.
The second bit is relatively mi
10 matches
Mail list logo