[po]

Yes, if it is accepted into the core then it means you will be able to run Django on Python 3 soon. Keep in mind though that:

* This port was basically done in a week so many parts still need analysis and discussion. It's a huge step though.

* When Django says 'soon' it might not be what you expect if you are not used to the project. This is the type of thing that depends on a ton of compatibility testing. Django makes very measured, deliberate steps and this will likely not make the 1.4 release.

* Your Django project may depend on non-python3 libraries that keep you on the 2.x branch. You have to make sure all of your libraries are compatible. This does increase the pressure on those libraries to get compatible though. (See http://python3wos.appspot.com/)

[briancurtin]

> * This port was basically done in a week so many parts still need analysis and discussion. It's a huge step though.

This was built on top of existing work which was started years ago. For a lot of people it did appear come out of nowhere, but it wasn't like Vinay just woke up Monday morning and figured it all out right away.

[jdunck]

There is no 2.x branch. This is a single codebase capable of running on both py2 and py3.

[po]

A bit confusing… sorry. I meant to say the 2.x branch of python not Django which I suppose is not really considered a branch but a whole other thing.

[Tobu]

The 1.4 release is still a ways off and hasn't been branched off from the master; chances are this will be in 1.4.