Hacker News Reader

This is also what I heard as of a year or two ago, but I think its becoming a progressively more outdated piece of advice as the world of Python 3 libraries catches up with 2. But certainly, Python 2.7 is still being written widely, and will remain so for awhile.

I don't think the issue is new code, so much as it's all the old code that needs supporting.

Also, library support still isn't 100% there. So, if one critical piece of your stack isn't on 3.x, you've gotta throw out the whole thing that stick with 2.x.

The biggest issue is that there's no real compelling reason to migrate away from Python 2 now. It's not meant to be an attack on Python 3 - Python 2.7 is still well-supported, and is plenty good enough for a lot of us.

That said, if I were starting out now, I'd start with Python 3.

almost every finance shop in nyc that is using python is using python 2.7. And yes - for new code as well.

Think of Python 2 and Python 3 as different languages with the first having a larger ecosystem and slightly better performance in some common workloads on the main implementation.