Re: About *Fields, newforms and lazyness

2007-03-21 Thread David Larlet
2007/3/6, David Larlet <[EMAIL PROTECTED]>: > Hi, > > I got some troubles today with newforms. I use to create models fields > with a first implicit verbose_name argument: > email = models.EmailField("E-mail") > > Unfortunately newforms fields have quite similar argument (label) but > it's not

Re: About *Fields, newforms and lazyness

2007-03-07 Thread Rubic
On Mar 7, 3:57 am, "David Larlet" <[EMAIL PROTECTED]> wrote: > Given the fact that label is not always at the same argument place, I > doubt that it breaks previous code because you "need" to specify > label= I must have been thrown off by "maybe we can reorder arguments" in the original post.

Re: About *Fields, newforms and lazyness

2007-03-07 Thread David Larlet
2007/3/6, Rubic <[EMAIL PROTECTED]>: > You'd be breaking the code of early newforms adopters for an arguable > benefit. It wouldn't affect my development base since I explicitly > use label=, but I can imagine other users might get irritated. Given the fact that label is not always at the same

Re: About *Fields, newforms and lazyness

2007-03-06 Thread Rubic
On Mar 6, 10:43 am, "David Larlet" <[EMAIL PROTECTED]> wrote: > I know it's easy to type label= for all newforms fields but maybe we > can reorder arguments in newforms before 0.96? What's your opinion > about that? Am I the only one? -0 You'd be breaking the code of early newforms adopters for

About *Fields, newforms and lazyness

2007-03-06 Thread David Larlet
Hi, I got some troubles today with newforms. I use to create models fields with a first implicit verbose_name argument: email = models.EmailField("E-mail") Unfortunately newforms fields have quite similar argument (label) but it's not the first argument. Moreover, it's a bit annoying because I