> I don't think that security matters enough to block Python at startup.
> Python has a long history of being a thin wrapper on top of the OS.
> Usually, Python doesn't workaround design issues of OSes, but expose
> functions as they are.

That's fine, so make a new function that will return "maybe random data maybe not, who knows" instead of taking the function for producing cryptographically secure random data and making it less suitable for that task. This is the problem, not that Python start up is blocking, but that this patch takes that edge case, and declares that it's behavior is the correct behavior for everyone trying to get cryptographically secure random numbers.