Tutorial and max_length (was Re: Time for a new release?)

0 views
Skip to first unread message

James Bennett

unread,
Aug 26, 2007, 12:19:22 AM8/26/07
to django-d...@googlegroups.com
And after we checked in an updated tutorial with admonitions
explaining the exact source of the error for those who run into it, we
*still* got someone opening a ticket telling us the tutorial needs to
use "maxlength" instead of "max_length".

How about if we just go back to "maxlength" for even the SVN tutorial,
and hold off changing the tutorial until the latest available release
of Django includes support for it? I don't normally like to cover for
people who can't be bothered to read *multiple* warnings telling them
not to shoot themselves in the foot, but this is just getting
ridiculous.


--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

SmileyChris

unread,
Aug 26, 2007, 6:14:40 PM8/26/07
to Django developers
On Aug 26, 4:19 pm, "James Bennett" <ubernost...@gmail.com> wrote:
> How about if we just go back to "maxlength" for even the SVN tutorial,
> and hold off changing the tutorial until the latest available release
> of Django includes support for it?

Reverting trunk documentation due to stupidity is just silly.

I say we just keep closing tickets until the next release, at which
stage we make the latest release docs the default.

Russell Keith-Magee

unread,
Aug 26, 2007, 7:59:23 PM8/26/07
to django-d...@googlegroups.com
On 8/26/07, James Bennett <ubern...@gmail.com> wrote:
>
> And after we checked in an updated tutorial with admonitions
> explaining the exact source of the error for those who run into it, we
> *still* got someone opening a ticket telling us the tutorial needs to
> use "maxlength" instead of "max_length".

Sigh...

> How about if we just go back to "maxlength" for even the SVN tutorial,
> and hold off changing the tutorial until the latest available release
> of Django includes support for it? I don't normally like to cover for
> people who can't be bothered to read *multiple* warnings telling them
> not to shoot themselves in the foot, but this is just getting
> ridiculous.

I can't say I'm wild about this idea. This has the potential to just
reverse the problem - people that are trying the SVN version are going
to try the tutorial, and start logging bugs about the tutorial being
out of date.

I think we've just about hit the limit of what we can do here, short
of cutting a release. IMHO we've reached the point where we will just
have to live with the problem until we cut the next release.

Yours,
Russ Magee %-)

Reply all
Reply to author
Forward
0 new messages