Marc-Andre Lemburg added the comment:
On 08.06.2016 22:49, Larry Hastings wrote:
>
> Third, because the os module is in general a thin wrapper over what the OS
> provides, I disapprove of "cryptorandom()" and "pseudorandom()" going into
> the os module. There are no functions with these names
Larry Hastings added the comment:
I am increasingly convinced that I'm right.
--
First, consider that the functions in the os module, as a rule, are a thin
shell over the equivalent function provided by the operating system. If Python
exposes a function called os.XYZ(), and it calls the OS,
Colm Buckley added the comment:
@pitti -
We already discussed this; there are cases where it's not practical to set an
environment variable. The discussion eventually converged on "it is not
desirable that Python should block on startup, regardless of system RNG status".
Re: the triggering bu
Martin Pitt added the comment:
> you could give some kind of command-line flag
That already exists -- set PYTHONHASHSEED=0.
> But I'll let someone else have the joys of negotiating with Lennart, and I
> won't blame the Python devs if using GRND_NONBLOCK unconditionally is less
> painful than
