From 58173068844ab8f2da810b669c8c0fdb78d86aee Mon Sep 17 00:00:00 2001
From: Victor Stinner <victor.stinner@gmail.com>
Date: Fri, 20 Mar 2015 12:18:51 +0100
Subject: [PATCH] PEP 475: add another article to explain why close() is not
 retried on EINTR

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

diff --git a/pep-0475.txt b/pep-0475.txt
index 6cfc02f4f..c0db35658 100644
--- a/pep-0475.txt
+++ b/pep-0475.txt
@@ -191,8 +191,13 @@ doesn't recompute the timeout yet)
 
 ``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