r/Python • • May 26 '14

Python 3 is killing Python

https://medium.com/@deliciousrobots/5d2ad703365d/
0 Upvotes

147 comments sorted by

View all comments

69

u/willm May 26 '14

I may have agreed with this a year or two ago. Not now though. The situation is way better than it used to be, and only improving.

Developing a new module to run on both Python 2 and Python 3 is also much less of a pain than it used to be. Particularly if you follow the advice on (http://lucumr.pocoo.org/2013/5/21/porting-to-python-3-redux/). It does make your code less beautiful than a pure Python 3 code base, but that is the price you pay for compatibility.

My biggest porting headache was adding Python 3 support to PyFilesystem. It was tricky because this library is an abstraction layer for files, which work quite differently in Python 3, and we didn't want to have to write everything from scratch. I have ported another, much larger project, in a day. It was tedious work, but no major issues.

But these problems only effect library developers. If you're building an application, just use Python 3. Most libraries have Python 3 support, and most of the ones that don't are probably not actively maintained any more.

3

u/shadowmint May 26 '14

If you're building a new application...

10

u/willm May 26 '14

If it's an app you probably aren't concerned about it running on both Python 2 and Python 3.

6

u/flying-sheep May 26 '14

true! you totally may go nuts with asyncio, enums, pathlib, and all the goodies!