[Python-checkins] peps: PEP 475: add another article to explain why close() is not retried on EINTR

[victor.stinner]

https://hg.python.org/peps/rev/d6d28b20939f
changeset:   5733:d6d28b20939f
user:        Victor Stinner <victor.stinner at gmail.com>
date:        Fri Mar 20 12:18:51 2015 +0100
summary:
  PEP 475: add another article to explain why close() is not retried on EINTR

files:
  pep-0475.txt |  9 +++++++--
  1 files changed, 7 insertions(+), 2 deletions(-)


diff --git a/pep-0475.txt b/pep-0475.txt
--- a/pep-0475.txt
+++ b/pep-0475.txt
@@ -191,8 +191,13 @@
 
 ``os.close`` and ``close()`` methods are a special case: they will ignore
 EINTR instead of retrying.  The reason is complex but involves behaviour
-under Linux and the fact that `the file descriptor may really be closed
-<http://lwn.net/Articles/576478/>`_ even if EINTR is returned.
+under Linux and the fact that the file descriptor may really be closed
+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

-- 
Repository URL: https://hg.python.org/peps