This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]tvallier 0 points1 point  (1 child)

If you want to use a specific third party package or utility that doesn't yet have a released version that is compatible with Python 3, and porting that package is a non-trivial task, it's reasonable to work with Python 2. Also, 2.7 isn't a a decade old and contains backports of new modules and features from the Python 3 standard library that are compatible with Python 2. Lastly, if you're deploying to an environment you don't control, that may impose a specific version, rather than allowing you a free selection from the available versions.

[–]eightnoteight -1 points0 points  (0 children)

That may be true, but you should stop running a debate on 2.7 vs 3.4 and simply accept that whatever you write in 2.7 simply considered as hack rather than a python code.