> A new library release that ‘adds support for Python 3.14’ is very likely to include other changes in the same release that may or may not be trivial There's

> A new library release that ‘adds support for Python 3.14’ is very likely to include other changes in the same release that may or may not be trivial There's no reason to believe that would be the case. The exceptions are: - add support for Python 3.0 (that's of course a very different situation as I described before) - eagerly adopt TONS of Python 3.14-only features (of course that means a different thing than "adds support for") What a specific release claim to do is irrelevant. The library should run its test suite in CI against multiple Python versions. in this specific case, updating to 3.14 just mean that the library stopped using bare excepts, which means that all version of Python pre-3.14 would still be able to use the library as usual (and thus, CI of those python versions can be retained). If you're running a library with a version of Python against which it's not tested, of course you're in a precarious situation (and a bug that silently causes your code to behave differently is going to be a lot more tricky to deal with than a bit of syntax which is not supported anymore).