I'm personally not a fan of depending on 2to3 or 3to2 at installation
time. Call it paranoia. Forking the project is also un-fun. I much
prefer to maintain a single project that's compatible with 2.6 through
3.2+, which is what I've started to do in my `py3k-compat` branch,
although I'm still getting familiar with the codebase and don't
consider the work to be especially merge-worthy.