I've yet to have any python feature/function/API change on me between minor versions. Yes, the big 2->3 thing did happen, and there were a few breaking changes

I've yet to have any python feature/function/API change on me between minor versions. Yes, the big 2->3 thing did happen, and there were a few breaking changes that came along with that. And I've been the semi-proud owner of codebases that had to simultaneously cater to versions 2.5, 2.7 and 3+ at the same time. Other than the print statement, new forms of try-catch statements and the obvious addition of type-hints eventually, I've always been able to make the code cater to all three versions. Eventually, 2.5 fell away, then 2.7 fell away, and now it's just 3+, which has been a breeze. These days I'm excited to install the latest version, and I don't even worry about any breaking changes. I'm also the type of person that doesn't do version-pinning as I think the concept is an anti-pattern that came from the JS world as a way to manage the chaos borne-about by the constant API changes, thousands of tiny libraries, and library dependency updates that it circularly-co-caused.