Most Python libraries are considering and/or starting a port now. Py3 is just now starting to be taken seriously, which is fine by me; we don't need to rush to use the "latest cool thing" as long as we get there eventually. It's good for Py3 to be tested and developed without being flooded for its initial lifecycle, which is what happens here.

Note that this attitude has mostly been guided by the Python Foundation in the first place. Until a few months ago, Python 2 was still actively developed. It has entered maintenance mode with 2.7; all future features or enhancements now go to Py3.

Again, please note that 2.7 was released only about six months ago. Since then, libraries, distributions, and other major players that push normal users to adopt new stuff have been moving to Python 3. As popular low-level libraries make the move higher-level stuff will begin to consider it too; Django's reason for not porting to Python 3 is basically "none of our dependencies run there yet".

This post actually demonstrates the strength of Python 3; while the author doesn't feel that this library specifically is a good candidate for a port, he is thinking about it, and he recommends that users still prepare for the transition. He says, in effect, "write code so that 2to3 can handle it easily when the moment comes", not "give up on Python 3 entirely".