I also found that maintaining single code base for both 2 and 3 is the only sane way. Running 2to3 during build is just too intrusive.
I liked the approach of 'six', but it is not shipped as a system module. Having something like that as a default system module in Python 2.6, 2.7, and 3.x would go a long way towards adoption of Python 3.
I found that I end up either using six or implementing some subset of it if I do not want to introduce the dependency.
I liked the approach of 'six', but it is not shipped as a system module. Having something like that as a default system module in Python 2.6, 2.7, and 3.x would go a long way towards adoption of Python 3.
I found that I end up either using six or implementing some subset of it if I do not want to introduce the dependency.