Well, start with porting something that you yourself uses. If you don’t know how, it’s true that the documentation is *very* lacking at the moment. I’m writing an series of articles in The Python Magazine starting in the January issue, those might help.

Generally, anything with the words “Enterprise” or “Proven” in them tend to be technological anchors.

But putting it into Python 3 for the “sole” purpose of being the carrot — when in fact it currently runs with python 2.X — that’s a little bit questionable.

How? (and not only do I don’t see how it’s broken, I do find it much better than the previous one especially when doing anything beyond a vanilla print)

> We can no longer format strings the old fashioned way.

You are wrong. The ‘%’ operator is considered obsolete in Python 3, but it’s still here: http://docs.python.org/3.1/library/stdtypes.htm…

IOW, you don’t give any justification to your first declaration and the second one is plain wrong.

> Python 3k didn’t.

Python 3 is a better and more useable language than Python 2 on pretty much every front. The only thing it’s missing is libraries adoption, and I trust that this will right itself within a year or two at worst.

As for where to begin, I have an idea for an index like you suggest — I need to think about it more and find someone willing to push it out, as I’ve got a pile of Other Really Important Things to Do. :(