[letmeinhere]

Python doesn't use semantic versioning. The number after the first period is a major (annual) release and can and does contain breaking changes (though so far never on the scale of the 2->3 upgrade).

We may never see a 4.0 because of the scar tissue, but the language continues to evolve.

[infamia]

> We may never see a 4.0 because of the scar tissue, but the language continues to evolve.

They should do the opposite really. If it hurts, do it more often and get better at it. A perfect time would be when Python gets some nice JIT performance improvements which everyone will probably like.

[sph]

Linux: let's bump the major version just because

Python: for the love of God [1] don't touch the version

I wonder if the scar tissue will ever heal and we'll see a Python 4 in two decades.

1: https://www.youtube.com/watch?v=asUyK6JWt9U

[sgarland]

K8s: the major version will never change, so instead we’ll introduce breaking changes with minor versions.

[hnlmorg]

Probably not before a Perl 6