Django 1.5 is in python 3. Soon it shall be so.

Though, MySQL-python, South, and Fabric are still red. South and Fabric make django projects so much easier to deal with, especially once deployed. It will be interesting to see what happens when 1.5 is released. I presume they'll be released along with 1.5, or follow right on the heals of it?

> Django 1.5 is in python 3

Django 1.5 has experimental Python3 compatibility.

Well yes, they said it isn't recommended in production. But, it's definitely a step forward.

Fabric depends on Paramiko, which is still red anyway.

Ruby 2.0 won't introduce as many incompatibilities, though. Something like the 2to3 tool wouldn't be needed. Most code is just expected to work as is.

I'm waiting for Python 3 to become de facto for newer/active libraries. Right now there's still a little standoffish demeanor about Python development for the future. I'd want to write in 3 but some important libraries are still backed up, so you're kinda forced to learn the idiosyncrasies of the porting scenario even though you'll most likely not need to know that 2 years from now when Python 3 is king.

Perhaps because the gains from Ruby 1.9 compared to 1.8 were a lot more enticing the community ported the libraries pretty swiftly. I don't see much hurry in the Python community, and some even talk about not porting at all.

That day could be today, for Django.