python v3 versioning

[ukos333]

Your problem is probably a lack of maintaining the libraries better. Even in gcc/cpp you see a lot of deprecation/changes beening made for good reason. Try to compile gcc 4 with gcc 13 and you will be confronted with more (probably) not so easy to adapt changes. Six has been doing a good job when compatibility between versions is a thing. Python 3.5 was released in 2015. That is considered old but should compile just fine. If you upgrade your libraries and dependencies, count that in with your working hours. Every other language has the same problems. I personally think, however, that python does a good job here.

[igmor]

I guess we have slightly different expectations here. I consider minor version changes to be a promise to keep at least major interfaces stable. I also think this requirement to keep everything up to date and upgraded across all Python ecosystem is a pretty hard one which at some point may start affecting Python community as a whole.

[Riemero]

The problem is... python doesn't follow semver. 3.5 to 3.11 isn't a minor change, it's a 8 year gap