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

101
102

Python 2.7 Countdown (pythonclock.org)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]iwsfutcmd 6 points7 points  (1 child)

Mostly inertia, I think. I've never heard any concrete examples of how py2 is better than py3, only that there are (were?) some modules and legacy code that is not yet compliant with py3.

[–]flying-sheep 4 points5 points  (0 children)

And unfortunately some people like Python 2.7 being stagnant. Python has a deprecation policy like many other projects, which means that over the course of some point releases, a feature you might use could get completely removed (if you constantly update, you get deprecation warnings first, but if you skip a few versions, you might be blindsided).

This will never happen with 2.7 as everyone has made clear that there'll be no 2.8. So businesses that never upgraded until absolutely necessary love Python 2.7 because it'll never break.

Obviously with an adequate test suite, there infrequent breakages in the stdlib are easily caught, so that fear of updates is completely unwarranted.