3 ms·
I got on python-dev recently and tried to make the case that breaking changes should be delayed to a X.0 release. It didn’t get very far, they seemed to determ
by mixmastamyk 7y ago
I got on python-dev recently and tried to make the case that breaking changes should be delayed to a X.0 release. It didn’t get very far, they seemed to determined to keep the current low predictability system.
The response was they don’t have enough manpower. The though ignoring deprecated stuff a few releases doesn’t sound particularly hard. I suspect Guido just likes it that way.
Btw, almost no one supports forward compatibility.
- EdwardDiego 7y agoIf you parse Python 3.8.2 as Python3 8.2.0 then the versioning follows semver nicely.
- pix64 7y agoThen you end up with Python 2 vs Python 3
- mixmastamyk 7y agoThey've had small breaking changes on many minor releases. The difference is the scope of the breakage. Python 3.0 broke every project. Python 4.0 certainly wouldn't, they are very timid now. In comparison, these breaks are tiny in scope.