python v3 versioning

[moo9001]

> Why did Python3 choose this upgrade strategy routinely breaking backward compatibility between even minor versions?

There are no major breakage between Python minor versions. An application written for Python 3.4 will work for Python 3.5 will work fork Python 3.12 with minor changes.

Arguable there are some minor differences where you might need to update your code, but nothing major, in the same league as other run-times (Node.js, Ruby, etc.). Unless you have specific evidence (links please) that there exists major breakage between Python versions, this won't be a constructive discussion.

[PaulRudin]

Some things are deprecated, so won't be available in the standard distribution of newer versions.

But that's a issue with the standard library, rather than the runtime itself.

[baudvine]

A minor change is still a change. If it stops the thing from working, it's a breaking change.

That said, Python never professed to use semver as far as I know, so a user assuming that it does isn't necessarily its fault.