We work closely with Linux distribution providers, and a number of us work *for* commercial Linux distributors (most notably Red Hat and Canonical).

Linux distributions have already agreed that Python 2.7 is in maintenance mode, and already influence the process of backporting any Python 3 changes that they consider sufficiently valuable to their users.

(For example, Red Hat has backported the SSL/TLS improvements to the system Python in RHEL 7 and to the Python 2.7 Software Collection after OpenStack developers at Rackspace convinced myself and others that the old behaviours were genuinely problematic)

Thus, is you want to convince us that this is a bug that actually needs fixing rather than a new feature request, you need to come up with a convincing explanation for why no Linux distribution (whether community run or commercial) has seen fit to report it as a bug at any point in the past 15 years.