Aha, sorry the models changed I was looking in newforms for maxlength.
My mistake
--~--~-~--~~~---~--~~
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@goo
On 9/1/07, onno <[EMAIL PROTECTED]> wrote:
>
> Well it is still in the docs so. Maybe adjust it a soon a possible so
> people will start the correct version.
If you find a location in the documentation that still refers to
maxlength, it is in error. We have tried to find all the references to
max
Well it is still in the docs so. Maybe adjust it a soon a possible so
people will start the correct version.
thx
On Sep 1, 11:25 am, SmileyChris <[EMAIL PROTECTED]> wrote:
> (well at least this is a different complaint than normal)
>
> On Sep 1, 9:00 pm, onno <[EMAIL PROTECTED]> wrote:
>
> > In
(well at least this is a different complaint than normal)
On Sep 1, 9:00 pm, onno <[EMAIL PROTECTED]> wrote:
> In the models we write maxlength
Hi Onno,
Not any more you don't. Check out the latest svn version (but we've
still kept it backwards compatible, so it still works with maxlength
too).
In the models we write maxlength
in the form we write max_length?
Why is there this diffrence? Is that logical?
Onno
PS. thanxs for writing Django.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developer
On Mar 21, 9:03 am, "Brad Fults" <[EMAIL PROTECTED]> wrote:
> Though, now I'm concerned that max_length on the Field is different
> from maxlength (the HTML attribute) on the Widget, which are
> frequently specified *right next to* one another. This seems
> undesirable.
It's not that "frequent" t
On Mar 20, 12:14 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> Hey Brad,
>
> This thread will answer your question:
>
> http://groups.google.com/group/django-users/browse_thread/thread/a4e0...
>
> Adrian
OK, at least it's an intended change. :)
Though, now I'm concerned that max_length on t
On Mar 21, 5:27 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 3/20/07, Brad Fults <[EMAIL PROTECTED]> wrote:
>
> > Is there a specific reason that newforms' Fields are using an
> > inconsistent name? If not, I suggest that these all be normalized to
> > "maxlength" and "minlength".
>
> Act
On 3/20/07, Brad Fults <[EMAIL PROTECTED]> wrote:
> In the newforms module, certain Fields have max_length and min_length
> attributes [1]. This seems strange because the models API uses
> maxlength [2] (note the lack of underscore), as does HTML [3], seen
> when creating Widgets in newforms.
>
>
On 3/20/07, Brad Fults <[EMAIL PROTECTED]> wrote:
> Is there a specific reason that newforms' Fields are using an
> inconsistent name? If not, I suggest that these all be normalized to
> "maxlength" and "minlength".
Actually, the plan over the next couple releases is to normalize to
"max_length"
In the newforms module, certain Fields have max_length and min_length
attributes [1]. This seems strange because the models API uses
maxlength [2] (note the lack of underscore), as does HTML [3], seen
when creating Widgets in newforms.
Is there a specific reason that newforms' Fields are using an
11 matches
Mail list logo
