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 nijel
Recipients nijel
Date 2011-01-04.13:42:42
SpamBayes Score 0.0034155366
Marked as misclassified No
Message-id <>
Currently if /dev/urandom does not provide any data, unradom() call is just stuck infinitely waiting for data.

I actually faced this issue when /dev/urandom was empty regular file (due to bug in pbuilder, but I don't think it matters how it did happen) and urandom() call just hang. I think it would be much saner in such case to throw an error and let user know that something it wrong than waiting infinitely.
Date User Action Args
2011-01-04 13:42:44nijelsetrecipients: + nijel
2011-01-04 13:42:44nijelsetmessageid: <>
2011-01-04 13:42:42nijellinkissue10824 messages
2011-01-04 13:42:42nijelcreate