Python 4 is already mentioned in the timelines for many of the changes. But not to worry, it will be much less of an issue migrating from 3->4 than it was from 2->3.
Guido is on the council and was the top vote getter by 30% or so. He was the only council member that got over 50% and cleared that easily. He's quite popular among the core devs.
Yes, but I think this is a case he doesn’t feel strongly about but that he still considered his decision / matter of taste when he was BDFL. And such cases will now be voted on, and if the others say “not doing semver is confusing and people will be scared by upgrading to 4.0” there won’t be strong arguments against that.
“not doing semver is confusing and people will be scared by upgrading to 4.0”
Python does not follow semver. You don't need to vote to keep the status quo. You vote to change it. If you really want semver, propose a PEP, but don't be surprised when it gets shot down.
Python implements large breaking changes in major versions. It implements small breaking changes in minor versions.
Or you store them up and break everybody's code in one fell swoop and have a Python 2->3 transition on your hands. I much prefer not following semver for that reason. I tried semver and it was a pain.
I much prefer a few minor changes preferably with deprecation warnings for a bit and then breaking things, similar to how numpy does it.
58
u/hopeinson May 30 '19
Now that you have heard of Python 3, now get ready for Python 4! [/s]
But seriously, we need to start moving on from Py2. It's a dead horse meat now.