Django is one of the best documented projects I have ever seen. But I know people who have problems with the way the documentation is structured. For some parts you have to understand a completely different part of the framework to follow the documentation. This is to some degree a price you have to pay for a complex framework and is IMHO fine.
But especially for those people is a book, which gives a structured way through the whole framework, a great thing.
I like the django documentation but sometimes I find it hard to figure out how to do exactly what I want to do ... the source code however is pretty readable, effectively it is cross referenced since you can look at the imports, and on github you can find the tag for the version you're using and browse it online.
A tutorial and a book solve completely different problems. A tutorial will only help you if you know what you want to achieve, and can therefore search for the tutorial. You read a book to find out about functionality you didn't know was there, lest you need it in the future.
An organized approach to "here are all the things we do" is definitely appropriate for the core documentation.
I just started learning Django(going through the tutorial today).
Is the Django Book ready to use as it is to learn Django? The Django docs I think are not enough for someone starting out learning their first web framework(they seem to go deep right away and don't provide a structured way of learning).
Also are the changes done on Github published on the book website or better to grab it directly from Github?
> Is the Django Book ready to use as it is to learn Django? The Django docs I think are not enough for someone starting out learning their first web framework(they seem to go deep right away and don't provide a structured way of learning).
It's pretty outdated by now, so you'll likely spend more time checking the differences (i.e. class based views). Same goes for Practical Django Projects.
You're best off looking at some online tutorials, another Django Book, or thinking of something to build and approaching it from scratch. Django's docs are very good, and there's a lot of open source projects out there that have likely accomplished something similar.
PS: I'm disappointed Reinout van Rees book was canned
Ebooks are just great when learning especially on dual screen setups. AFAK Rails books get updated really fast - and there are at least a few good introductory courses. There is a Django video series coming but who can wait untill December :)
The Django tutorial just doesn't have the depth that the rails book does in my opinion. Though, it's well written and awesome in it's own way. There is also a lot of other well written guides on the rails main site
Following another user advice in the thread I started learning using the updated django book and I must say is great so far( I am at chapter 3). I have previosuly looked over the rails book and this is better for a newcomer.
I completely dismissed the django book for being outdated when starting to lear Django, despite people recommending it to me ...nice to know others won't have to dismiss it the same way as some chapters seemed really well written
Python 3 support was --last I heard-- still considered experimental/alpha by the core team in the upcoming Django 1.5 release, so I would assume if it treats it at all, it will be mostly to encourage forward-compatible programming practices.