Łukasz Langa <luk...@langa.pl> added the comment: Thanks for reporting, Ned. I agree with Mark though.
We've done 7 releases of Python 3.9 already. The later in the release cycle for a given Python version, the less it's clear if it's "worth" performing complex fixes. Most importantly because introducing a large functional change at this point is risky and we try hard not to disrupt users of stable versions. Moreover, our experience shows that later bugfix releases see decreasing adoption because by default downstream distributors keep their original early bugfix versions of Python with only security- and build-related fixes ported from later releases in the same series. ---------- resolution: -> wont fix stage: -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44672> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
