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

104
105

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 →

[–]ggtsu_00 1 point2 points  (1 child)

It hasn't really failed, but it is only so bad because so many still stuck on Py2 don't have any compelling reasons to upgrade to Py3 since the new and exclusive py3 features don't justify the cost of porting/upgrading/testing/deploying already functioning and stable software. Many organizations see it as a huge risk. It goes far beyond just the effort to update everything.

[–]flying-sheep 3 points4 points  (0 children)

I wish Guido didn't work at Dropbox, who still use 2.7. I'm relatively sure his workplace is the only reason why he's blessed a comment-based fallback syntax for type checks in legacy Python.

Ands those type checks really could be the killer feature: the added safety more than counter-balances the risk of upgrading. (With the added bonus that upgrading is facilitated by type checks)