If this doesn't get fixed, doesn't that mean the Python review process is flawed? Sure, Python is an open source project and many people just work in their free time. But this doesn't really apply here, does it? The bugfix is available. Only a review is required. All this is happening while new features get added to Python with every new minor version. While the bug is allowed to live there. Please help me understand how this can happen.
I think there's a misunderstanding here -- you seem to imply that producing a bugfix is work that takes somebody's time, while reviewing a bugfix is not work and doesn't cost anything. But realistically, for most issues, things are the other way around -- writing the code is easy (at least to a core dev :-) but reviewing code is a gut-wrenching process that takes up emotional energy and a lot of time. Given the discussion in the issue corresponding to the PR it is clear that that is what is going on here.
As Nadia Eghbal writes in her book _Working In Public_, *maintainer attention* is actually the scarcest resource in many open source projects, and Python is no exception. It is also the least satisfying kind of work, which is why volunteers prefer to work on new features.
I love Python. No hard feelings. But this is really bugging me and I can't help but feel disappointed.
Thank you for that! Hopefully all the responses you are getting help you see why this is not so simple.