The Linux 2.5, Ruby 1.9 and Python 3 release management anti-pattern

Re:The Linux 2.5, Ruby 1.9 and Python 3 release management a... by TylerE on Monday December 26, 2016 @10:15PM (#13261058)

Ultimately, I think Python 3 had exactly the wrong amount of breakage. They either should have broken way less (e.g., let 2.x code run largely unchanged if it didn't deal closely with unicode) or should have broken more, to give more of carrot... like if some of the new async stuff could have been available in 3.0, that would have given some people a reason to move right away.

[ Parent | on HN ]

Re:The Linux 2.5, Ruby 1.9 and Python 3 release management a... by freehunter on Tuesday December 27, 2016 @12:25AM (#13261452)

I kind of feel like that's why print changed. It's going to be used in almost every Python script at some point in time, so it forces a breaking change without causing a seriously major break by itself. It's enough to make your script need to be updated, but not enough to make you re-write it from scratch (possibly in another language).

[ Parent | on HN ]