> Python core library development is filled with asshats who like to deprecate naming conventions in later versions rather than just improving the existing libr

> Python core library development is filled with asshats who like to deprecate naming conventions in later versions rather than just improving the existing libraries and keeping the method names the same. I think this is a gross misrepresentation of both technologies, to the point that it goes well beyond a normal apples-to-oranges comparison. A shell script runs well on any standard-compliant implementation, just like python3.4 scripts will run exactly like they always did when running on a python3.4 interpreter. Python's libraries break when asshats "deprecate naming conventions" only when you somehow assume that, say, your python3.10 script would run on python2.7, or just like your shell script breaks when the program it calls happens to break it's cli. Also, is versioning still a problem given the pervasiveness of package managers with support for version pinning?