[issue23707] PEP 475: os.urandom() doesn't handle EINTR correctly

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue23707] PEP 475: os.urandom() doesn't handle EINTR correctly

Roundup Robot added the comment: New changeset e57b4d464d1c by Victor Stinner in branch 'default': Issue #23707: On UNIX, os.urandom() now calls the Python signal handler when https://hg.python.org/cpython/rev/e57b4d464d1c -- nosy: +python-dev ___ Pyt

[issue23707] PEP 475: os.urandom() doesn't handle EINTR correctly

Changes by Ned Deily : -- nosy: +neologix ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue23707] PEP 475: os.urandom() doesn't handle EINTR correctly

STINNER Victor added the comment: random.patch: fix the issue with the new _Py_read() function added by the issue #23708. -- dependencies: +PEP 475: Add _Py_read() and _Py_write() functions keywords: +patch Added file: http://bugs.python.org/file38560/random.patch _

[issue23707] PEP 475: os.urandom() doesn't handle EINTR correctly

New submission from STINNER Victor: dev_urandom_python() retries read() if it fails with EINTR, but Python signal handlers are not called: PyErr_CheckSignals() is not called. It's important be able to interrupt a function by a signal, especially if it's blocking. We need maybe a new _Py_read()