Re:Reasons Python Sucks
by erik_seaberg on Sunday January 15, 2023 @01:32AM
(#34387237)
3.0 or 4.0 is the time to drop a user-facing feature. If 3.11 is not backward compatible, they aren’t following semver. I won’t assume every minor version bump must break stuff, but I have to be aware that it might and budget time for fixes.
Does Python claim to follow semver? If not then I'm not sure what your point is.
Re:Reasons Python Sucks
by erik_seaberg on Sunday January 15, 2023 @02:07AM
(#34387372)
From https://peps.python.org/pep-0006/ it seems that 3.10.9 is expected to be compatible with 3.10.8, but users need to treat 3.11.0 as potentially a major rather than minor release. I wish they had labeled it 311.0 to communicate this and set expectations.
Eight, to be exact: 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10. Python 3.3 was released more than 10 years ago. That's a long time for a feature to be deprecated before being removed altogether.
> your script that works in python 3.x is not guaranteed to work in 3.y
True, not "guaranteed" in every single respect. But spotting and fixing a deprecation warning is pretty simple. So are fixes for other examples of feature removals (and I don't think there are that many in Python 3). That's nothing like the picture the author was painting; he was talking as if code needs to be "ported" between each version, which is just nonsense.