If that's a project for yourself, maybe you can use python 3.x if you don't depend on libraries which need python 2.x. If that's project you intend on distribu

If that's a project for yourself, maybe you can use python 3.x if you don't depend on libraries which need python 2.x. If that's project you intend on distributing, then please support python 2.x. First, given that python 3.x has few killer features compared to 2.x, it won't bring you much, frankly. Then using python 3.x in production is near impossible ATM for many people. Third, it is easy to forget that other people may have other dependencies than you, which means that even though you don't depend on python3, other people may want to use your package in an environment where python 3.x is not possible. Note that supporting python 2.x may mean different things. It could be that you restrict to the subset common to 2 and 3: while painful, it is possible, and some known packages have done it (ply I believe, for example). It could be that you write your code such as 3to2 can produce a workable solution (I have never used it, so cannot comment on it).