I've been using Python3 intensely for three or four years and have long forgotten Python2. I'm teaching my kids to program, and that means the living Python not the living dead zombie Python.<p>I work in other languages, too, but I'd like to switch to Python3 for webdev if practical. Part of that is the ongoing need to prune the garden of knowledge, so I can sharpen my focus on what I decide to keep. Part is because Python3 is the only language my kids know, and I'd like to get them involved in some of what I do.<p>I would consider Django if there were good resources, such as an edition of this book, that taught Django as a Python3 web framework. I don't know enough about Django to know what's reasonable, but if the Django community updates this book from Python-1998 to Python-2005 then my kids and I will check it out--when it goes on display in the Computer History Museum.<p>But if it is reasonable to aim the next edition of this book at pure Python3, I might be interested. Django itself might not allow it, for all I know, in which case the book I'm talking about would be irrelevant. I really don't know.<p>What I'd really like to find is a production-ready framework in which Python3 was the assumed language of the framework, docs, and community, and Python2, if mentioned at all, was the "special case" that was "experimentally supported."
For those like me who wondered why this was posted since the book content was out of date: The Django Book project needs help updating the book to cover Django 1.4 and beyond. Send pull requests to <a href="https://github.com/jacobian/djangobook.com" rel="nofollow">https://github.com/jacobian/djangobook.com</a>
It's slightly disappointing that the revision will not at all focus on Django 1.5 that would operate on Python3. Perhaps a few 'If you're doing this on Python3' side-notes will suffice?
Cool, although I remember when the Dojo Book was the primary documentation for Dojo Tookit before there was any reference. It was quite a frustrating experience. While books like these are useful, the book format is not a great main source of documentation for a library or a framework.