iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 475: add another article to explain why close() is not retried on EINTR

This commit is contained in:
Victor Stinner 2015-03-20 12:18:51 +01:00
parent e36583e224
commit 5817306884
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
pep-0475.txt
View File

@ -191,8 +191,13 @@ doesn't recompute the timeout yet)
``os.close`` and ``close()`` methods are a special case: they will ignore ``os.close`` and ``close()`` methods are a special case: they will ignore
EINTR instead of retrying. The reason is complex but involves behaviour EINTR instead of retrying. The reason is complex but involves behaviour
under Linux and the fact that `the file descriptor may really be closed under Linux and the fact that the file descriptor may really be closed
<http://lwn.net/Articles/576478/>`_ even if EINTR is returned. even if EINTR is returned. See articles:
* `Returning EINTR from close() <http://lwn.net/Articles/576478/>`_
* `(LKML) Re: [patch 7/7] uml: retry host close() on EINTR
<http://linux.derkeiler.com/Mailing-Lists/Kernel/2005-09/3000.html>`_
* `close() and EINTR <http://alobbs.com/post/54503240599/close-and-eintr>`_
InterruptedError handling InterruptedError handling