This tracker is only concerned with the PSF/python.org Windows and macOS installers, not the *nix distributions, so I assume that one the former is your concern.

For those, your request has been made and rejected multiple times before.  A request on the tracker won't change this policy decision.  Briefly, we consider other actions by the volunteers who make those installers to be more valuable.  Making more installers means not doing something else, like fixing bugs or keeping up with OS changes or enhancing something.

A little more: 1. Many -- maybe most -- security fixes are only or mainly of concern to server maintainers.  They mostly run *nix or compile their own binaries or pay someone to do so.  2. Running older Python versions instead of newer versions is a user choice, not ours.  3. Non-PSF distributors of Python for Windows and Mac are free to recompile their binaries whenever they want to.

For Windows, I don't know what your concern is about 'signed' binaries.  Anyone can install the Visual Studio Community Edition and Git and clone and compile their own binary.  This is at least as secure as a downloaded binary.  If more instructions are needed for how to use that binary for production use, that would be a different issue. (And perhaps git should be told to git-ignore additions to site-packages.)