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 pitrou
Recipients Claudiu.Popa, brett.cannon, christian.heimes, pitrou, virtuald, vstinner
Date 2017-12-19.15:22:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <713d34b8-9f4d-84cd-d6e8-066f374411ab@free.fr>
In-reply-to <1513695028.19.0.213398074469.issue29877@psf.upfronthosting.co.za>
Content
Le 19/12/2017 à 15:50, STINNER Victor a écrit :
> 
> Hum, it looks like an "embedded device", likely with no entropy source.

If it does I/O (which it probably does, being used for robotics), it
should certainly be able to extract entropy from the outside world.

If it doesn't, it's an OS implementation issue.

Of course it probably doesn't hurt to import concurrent.futures lazily.
However, people should generally not expect us to never call urandom()
when importing stdlib modules.
History
Date User Action Args
2017-12-19 15:22:49pitrousetrecipients: + pitrou, brett.cannon, vstinner, christian.heimes, Claudiu.Popa, virtuald
2017-12-19 15:22:49pitroulinkissue29877 messages
2017-12-19 15:22:49pitroucreate