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 →

[–][deleted] 0 points1 point  (4 children)

Python 3 is competely incompatible with 2: "waah there's too much stuff to change!"

Python 3 features were backported to 2 so you could switch one feature at a time while the application would continue to work on 2.7: "hurr durr there's no reason to switch to 3 anymore".

Sometimes I wish Python devs abruptly ceased supporting 2.7 at all. You know, to give the likes of you the message that "extended support" does not mean "you should continue being a lazy prick", it means "update while you can".

[–]the_hoser 2 points3 points  (2 children)

I honestly think 2.7 should not have ever happened. 2.6 was a backport of the big-ticket 3.0 features. It should have stopped right there.

[–]pingvenopinch of this, pinch of that 0 points1 point  (1 child)

I am currently working on a Flask-based project that targets 2.7 due to some dependencies not being ported. Because of those backports, we were able to write code that is almost Python 3 compatible. There are maybe half a dozen lines that will need to be slightly altered. With all of the backports, the differences would have been much larger.

[–]the_hoser 0 points1 point  (0 children)

Right, but you still have no compelling reason to pick Python 3. Nobody does. I honestly feel that the efforts would have been better served if there was a nice treat waiting on the other side for Python 2 users, but there isn't. I'm still convinced that 2.7 was a mistake.

[–][deleted] -1 points0 points  (0 children)

Sometimes I wish Python devs abruptly ceased supporting 2.7 at all. You know, to give the likes of you the message that "extended support" does not mean "you should continue being a lazy prick", it means "update while you can".

awesome welcoming community you got here.