News for hackers. Stuff that matters.

A comment on Python 3 in 2016. Parent comment

Re:Python 3 in 2016 by bhaak on Thursday February 18, 2016 @05:47AM (#11124912)
> Getting rid of the GIL is more noble, but seems impossible to do without breaking compatibility. > > Python 4 will just be the next release after Python 3.9.

Really? Why even change the major version then, when there are no breaking changes?

Given that many Python programmers seem to be traumatized by the last major version switch, why even bother?

Or is this just for setting up Python 5 can have breaking changes if the switch to 4 is painless?

[ Parent | on HN ]
Re:Python 3 in 2016 by orf on Thursday February 18, 2016 @06:54AM (#11125130)
> Really? Why even change the major version then, when there are no breaking changes?

Python releases don't follow semver. If Linus can bump the kernel to 4.0 because he felt like it so can Python.

[ Parent | on HN ]
Re:Python 3 in 2016 by dragonwriter on Thursday February 18, 2016 @09:27AM (#11125914)
> If Linus can bump the kernel to 4.0 because he felt like it so can Python.

"Can" is not "should": I mean, Python can go from 3.x to Python 2020, go with year numbers for a while, then have Python XP, then go Python 7, Python 8, Python 8.1, and then skip to Python 10. But there's no good reason to do that.

[ Parent | on HN ]