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 Colm Buckley
Recipients Colm Buckley, Lukasa, alex, christian.heimes, doko, dstufft, larry, lemburg, martin.panter, matejcik, ned.deily, python-dev, rhettinger, skrah, thomas-petazzoni, vstinner, ztane
Date 2016-06-07.13:58:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I have no objection to *deliberate* invocations of the system RNG blocking if needed. Presumably this behavior can be codified into the various APIs.

My objection is *entirely* to _PyRandom_Init() calling a potentially-blocking RNG source, before script parsing even begins. This basically prohibits Python from starting on systems where the system RNG is blocking. Linux is the only affected system *now* because the systemd crontab generator is the only Python script called before the RNG has initialized. Exactly the same issue would apply to any of the BSDs or Solaris, if /dev/urandom blocks as you describe. I want to be clear - this is not a Linux-specific issue.
Date User Action Args
2016-06-07 13:58:38Colm Buckleysetrecipients: + Colm Buckley, lemburg, rhettinger, doko, vstinner, larry, christian.heimes, matejcik, ned.deily, alex, skrah, python-dev, martin.panter, ztane, dstufft, Lukasa, thomas-petazzoni
2016-06-07 13:58:38Colm Buckleysetmessageid: <>
2016-06-07 13:58:38Colm Buckleylinkissue26839 messages
2016-06-07 13:58:38Colm Buckleycreate