[BobKabob]

I can't believe it... not one comment telling the django guys to quit celebrating and get back to work on a version that supports Python 3? :-)

Seriously, Adrian, Jacob, and the django team, I love your product. I actually just bought a SECOND copy of your book (available free on the web). What's wrong with this picture?

[Ingaz]

I really want downvote you.

Excuse me for arrogance, but it's not their fault that Django (or Pylons or Flask) can't work on Python 3.

Look at http://flask.pocoo.org/docs/foreword/

"Because of that we strongly recommend against using Python 3 for web development of any kind and wait until the WSGI situation is resolved. You will find a couple of frameworks and web libraries on PyPI that claim Python 3 support, but this support is based on the broken WSGI implementation provided by Python 3.0 and 3.1 which will most likely change in the near future.

Werkzeug and Flask will be ported to Python 3 as soon as a solution for WSGI is found, and we will provide helpful tips how to upgrade existing applications to Python 3. Until then, we strongly recommend using Python 2.6 and 2.7 with activated Python 3 warnings during development, as well as the Unicode literals __future__ feature."

[BobKabob]

I agree (except for the part where you wanted to down-vote me). I wasn't trying to say it was their fault. It was more a comment about other comments, not about the django guys.

I love django. But I also I can't wait for the day when we can quit talking about Python 2, and that Python 3 will be the obvious choice for ALL environments.

Considering Python 3K discussions go back to 2006 (PEP 3000) or earlier, and Python 3 was released in 2008, and we're still probably years away from closing the book on Python 2, it's just amazing how long it takes to "turn a battleship". This transition to Python 3 might be a decade or more, from start to finish! amazing!