This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author thomas-petazzoni
Recipients Colm Buckley, Lukasa, alex, doko, dstufft, larry, lemburg, martin.panter, matejcik, ned.deily, python-dev, rhettinger, skrah, thomas-petazzoni, vstinner, ztane
Date 2016-06-07.11:41:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The original problem is that Python wants to generate random numbers at *startup*. Are those random numbers really used for crypto-related activities? I doubt it.

So isn't the proper solution to have two functions, one delivering random numbers that are usable for crypto-related activities, and which would potentially block, and a second one that delivers random numbers that are not appropriate for crypto stuff. This second function can be used at Python startup to replace what is done currently.

It is most likely perfectly fine if Python blocks when explicitly asked to generate cryptographically secure random numbers. But not when simply starting the interpreter.
Date User Action Args
2016-06-07 11:41:58thomas-petazzonisetrecipients: + thomas-petazzoni, lemburg, rhettinger, doko, vstinner, larry, matejcik, ned.deily, alex, skrah, python-dev, martin.panter, ztane, dstufft, Lukasa, Colm Buckley
2016-06-07 11:41:58thomas-petazzonisetmessageid: <>
2016-06-07 11:41:58thomas-petazzonilinkissue26839 messages
2016-06-07 11:41:58thomas-petazzonicreate