3 ms·

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

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.

yen223 12y ago
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.