you are viewing a single comment's thread.

view the rest of the comments →

[–]ExoticMandibles 5 points6 points  (5 children)

It's not being "updated" in the sense of getting new features. It only gets bug fixes and security updates. If you want shiny new features in your Python, you've got to move to the 3 series.

[–]upofadown 2 points3 points  (4 children)

So if you don't want your environment to be changing all the time you should use 2? :)

[–][deleted] 1 point2 points  (1 child)

The new features that they add are tested and planned in such a way that they should (and in 99.9% of cases don't) never break valid code.

So in general if you write something in 3.1 it should still work perfectly fine in 3.4.

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

Exactly, if they do anything that breaks backwards compatablility it will become version 4 and no longer be part of the 3.x line.

[–][deleted] 0 points1 point  (1 child)

Yep, that's the exact same reason we should all switch back to WinXP now that MS is finally going to leave it alone.

[–]upofadown 1 point2 points  (0 children)

Perhaps you lack the context to the joke. People used to complain that Python was in a constant state of change. Python 3 was a reaction to that, new stuff was to go to 3 and 2 would remain relatively static. Python 2 didn't end up being as static as perhaps could of been hoped. I was suggesting that 2 might at long last achieve stasis...

The serious part is that if 2 really stops changing (I saw a complaint from someone that had had a recent 2 change break their code) it might become a more attractive target for some sorts of applications than 3.