[issue21207] urandom persistent fd - not re-openned after fd close
Steven Hiscocks
report at bugs.python.org
Sat Apr 12 23:09:50 CEST 2014
Steven Hiscocks added the comment:
I agree in part, but it's quite common to close fd's in some cases like in a child process after using "os.fork()". There is no way, as far as I'm aware, to identify which fd is associated with /dev/urandom to keep it open; or anyway to reopen it such that other libraries which depend on it can use it (for example "tempfile.TemporaryFile").
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue21207>
_______________________________________
More information about the Python-bugs-list
mailing list