Really early on they said Python 3 would break backward compatibility. Normally I'd bitch and moan but they gave us plenty of time and knew it would be a slow process.
Hopefully everyone will move to python 3 soon and we can just leave 2.x cleanly.
Once the Django community starts adopting Py3K, it's only a matter of time before the rest of the Python community follows suit.
Have a good migration :)
If not that, what sorts of work are they getting paid to do in Python?
And, what does it mean for developers using Django? Will I be able to run official Django 1.X on Py3k soon?
* 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/)
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.
Can someone (Vinay?) explain a simpleton (like me :)), the reasoning behind using the single-source approach?
In practice, I find this quite pain to deal with (2to3 is slow, hard to use when you need to support python 2.3 or 2.4, etc...), and much easier to just do the 2/3 compatible source codebase. Various projects use the same approach, but this is a tradeoff that will depend on a per-project basis.
"I'm a bit concerned that you didn't get in touch with us before you started with the work, since tracking the changes would have been easier. FWIW, Martin von Löwis, Alex and me would be those you can ask if you need any further help"
Unless I'm missing something, it seems fairly clear that Vinay Sajip (plus collaborators) did this entirely without the knowledge of the Django core team... or at least some of them!
Edit: you already responded over there, never mind.