New submission from Michal Čihař <mic...@cihar.com>: 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. ---------- components: Library (Lib) messages: 125316 nosy: nijel priority: normal severity: normal status: open title: urandom should not block type: behavior versions: Python 2.7 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10824> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
