Amazon: "Practical Django Projects" by James Bennett (June 2008)

[Dave U. Random]

http://snipr.com/PracticalDjango

[Stefan Scholl]

Dave U. Random <an*******@anonymitaet-im-inter.netwrote:

http://snipr.com/PracticalDjango

June 2008 is a bit too early. Django isn't ready.
--
Web (en): http://www.no-spoon.de/ -*- Web (de): http://www.frell.de/

[Fredrik Lundh]

Stefan Scholl wrote:

Django isn't ready.

That's a remarkably ignorant statement.

</F>

[Stefan Scholl]

Fredrik Lundh <fr*****@pythonware.comwrote:

Stefan Scholl wrote:

>Django isn't ready.

That's a remarkably ignorant statement.

The 1.0 release will be in September.
--
Web (en): http://www.no-spoon.de/ -*- Web (de): http://www.frell.de/

[Marc 'BlackJack' Rintsch]

On Thu, 17 Jul 2008 05:41:11 +0200, Stefan Scholl wrote:

Fredrik Lundh <fr*****@pythonware.comwrote:

>Stefan Scholl wrote:

>>Django isn't ready.

That's a remarkably ignorant statement.

The 1.0 release will be in September.

So what? It's not the version number that matters but features and
stability. It's not uncommon in open source projects to have very usable
software with a version number below 1.0.

Ciao,
Marc 'BlackJack' Rintsch

[Fredrik Lundh]

Stefan Scholl wrote:

>>Django isn't ready.

That's a remarkably ignorant statement.

The 1.0 release will be in September.

So? "1.0" will be done then, yes. In what way does that mean that
Django itself isn't ready, in any sane sense of that word?

(For bystanders, Django's 0.91 release in early 1996 was what most
people would have called "1.0". 0.95 was a "2.0" release, and the
upcoming 1.0 release is pretty much a "3.0". Or if you use Micro-
soft's numbering system, 0.91 was "3.0", 0.95 is "5.0" and 1.0 is,
what, "8.0"?)

</F>

[Stefan Scholl]

Marc 'BlackJack' Rintsch <bj****@gmx.netwrote:

On Thu, 17 Jul 2008 05:41:11 +0200, Stefan Scholl wrote:

>Fredrik Lundh <fr*****@pythonware.comwrote:

>>Stefan Scholl wrote:

Django isn't ready.

That's a remarkably ignorant statement.

The 1.0 release will be in September.

So what? It's not the version number that matters but features and
stability. It's not uncommon in open source projects to have very usable
software with a version number below 1.0.

The book is about the development version, which was current at
the time the book was written. See page 4.
Nobody says something about "Book after feature freeze" (or
similar). Instead I get "ignorant statement" and "usable
software".

My conclusion: This book isn't about a stable release and not
about a future stable release. (And even if it was about the last
stable relase, too much has changed and will change until
September 2008. IMHO.)
And by the way: The quote was changed by deleting something on
the same line:

"June 2008 is a bit too early. Django isn't ready."

vs.

"Django isn't ready."
--
Web (en): http://www.no-spoon.de/ -*- Web (de): http://www.frell.de/

[Fredrik Lundh]

Stefan Scholl wrote:

And by the way: The quote was changed by deleting something on
the same line:

"June 2008 is a bit too early. Django isn't ready."

vs.

"Django isn't ready."

Is this a language issue? That you meant to write "django 1.0 isn't
done" (as in "completed; finished") but accidentally wrote "django isn't
ready" (where "ready" is usually read as "completely prepared or in fit
condition for immediate action or use")?

(and the "stable release" and "much will change" stuff is pure FUD, of
course. what competing project will I find if I google your name?)

</F>

[alex23]

On Jul 17, 6:04 pm, Fredrik Lundh <[e-mail]:

Django's 0.91 release in early 1996

While I totally agree with position, I'm pretty sure you mean 2006
here :)

[bruno.desthuilliers]

On 16 juil, 10:35, Stefan Scholl <[e-mail]:

Dave U. Random <[e-mail]:

http://snipr.com/PracticalDjango

June 2008 is a bit too early. Django isn't ready.

Oh, really ? Too bad. But, wait... If Django isn't ready, what's that
framework I've been using for almost three years now, then ???

[Torsten Bronger]

Hallöchen!

br*****************@gmail.com writes:

On 16 juil, 10:35, Stefan Scholl <[e-mail]:

>Dave U. Random <[e-mail]:

>>http://snipr.com/PracticalDjango

June 2008 is a bit too early. Django isn't ready.

Oh, really ? Too bad. But, wait... If Django isn't ready, what's
that framework I've been using for almost three years now, then
???

Before writing sarcastic comments, reading the thread would be
really polite.

As far as versioning is concerned, Django's policy is that "1.0"
equals "API is frozen". And I consider publishing a book four
months before the API is polished bad timing, too. Especially
because Django is exquisitely documented on its webpage, so there is
no urgent need for it.

I thought about buying a Django book, too. I'm happy to have
delayed it, for the same reason Stefan mentioned.

Tschö,
Torsten.

--
Torsten Bronger, aquisgrana, europa vetus
Jabber ID: to*************@jabber.rwth-aachen.de

[Stefan Scholl]

Fredrik Lundh <fr*****@pythonware.comwrote:

(and the "stable release" and "much will change" stuff is pure FUD, of
course. what competing project will I find if I google your name?)

Found something? Maybe this could help me to choose a web
framework.
--
Web (en): http://www.no-spoon.de/ -*- Web (de): http://www.frell.de/

[Torsten Bronger]

Hallöchen!

Bruno Desthuilliers writes:

Torsten Bronger a écrit :

>br*****************@gmail.com writes:

>>On 16 juil, 10:35, Stefan Scholl <[e-mail]:

Dave U. Random <[e-mail]:

http://snipr.com/PracticalDjango

June 2008 is a bit too early. Django isn't ready.

Oh, really ? Too bad. But, wait... If Django isn't ready, what's
that framework I've been using for almost three years now, then
???

Before writing sarcastic comments, reading the thread would be
really polite.

You may not have notice, but applied to a piece of software,
"ready" is usually understood as "ready for production use". Which
Django is, and has been for years now.

Yes, so Stefan used the wrong English word. The rest of the thread
had already revealed it when you made your statement.

Tschö,
Torsten.

--
Torsten Bronger, aquisgrana, europa vetus
Jabber ID: to*************@jabber.rwth-aachen.de