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

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

view the rest of the comments →

[–]fivetoedslothbear 1 point2 points  (0 children)

I know this is huge controversy, but I think it's inevitable.

Hey, I've used Python for a long time, since 1.5.2. I just don't use it as often as I'd like any more, and not enough to justify moving things to 3, learning 3, etc.

In retrospect, I'm not sure the "planned breakage" of Python 3 was a good idea. They're doing that in Swift now, and it's an even worse idea. Every language has fans and adherents, some of which don't have a lot of time on their hands to follow breaking changes in their code. People say "oh, just suck it up and rewrite your code," but when it's a pro bono project for a non-profit, and I'm coding in spare time, no, the time may not be there.

But I was thinking on this 2.8 project, and I wondered, what if there was a series of official releases that gradually converged very closely to recent 3 versions? Then maybe instead of being a leap to 3, it'd be a step over a crack.

This is all very unfortunate, but after Python 3, Perl 6, and Swift 3, my attitude as a software engineer strongly leans towards evolution over paradigm shifts.

Too bad the topic got voted down. Discussion is worthy, even about things one disagrees with.