From what me and my coworkers have discussed we are basically all waiting on Django to get Python 3.x adoption. I've tried submitting multiple patches for this and helping Django as much as possible but they don't seem to want outside help.
Come on Django, come on, a lot of us are waiting for you.
The problem is and continues to be the social and community issue of gracefully deprecating our way out of Python 2.x, which we're basically doing at a rate of one Python version per Django release. All the patches in the world can't really make this process go faster :)
The situation hasn't changed. If you want to work with Django on Python 3, go ahead; the code's right there for you. We need the help: it's going to take a lot of burn-in to make sure we get everything right.
If you're waiting for it to hit trunk, fair enough I guess (though it's a purely arbitrary decision on your part; the only difference between the branch and what'll hit trunk is the URL). That should happen shortly after 1.4 ships, so quite soon now.
I simply like to keep myself up with the market/community, when I release new software I try and make sure I'm not releasing something on a platform that will be dead in a month.
My rule of thumb is write new stuff in Python 3, keep old stuff on Python 2 unless I have to rewrite it for some reason anyway.
Upgrading just to upgrade seems like developer problem more than a technical problem.
[1] http://blog.python.org/2011/07/python-launcher-for-windows_1...
As far as I can see, they're shipping both 2.7.2 and 3.2.2: http://pkgs.fedoraproject.org/gitweb/?p=python.git
Fedora 16 (the latest) ships with Python 2.7. Python3 is available in the yum repositories.
Distros aren't holding Python3 adoption back, it's apps and libraries.
You're confusing Fedora and Red Hat. Fedora is generally very cutting edge and has been shipping with 2.7 for quite a while now, Red Hat is far more conservative and was, at least up until the latest release, shipping with 2.4