[Python-checkins] cpython: Drop claim about nasty problem.

Mon Jun 6 10:28:26 CEST 2011

http://hg.python.org/cpython/rev/3301a01071f9
changeset: 70656:3301a01071f9
user: Martin v. Löwis <martin at v.loewis.de>
date: Mon Jun 06 10:27:56 2011 +0200
summary:
 Drop claim about nasty problem.
It's unclear what this was referring to; most likely, it was about sockets
that the application had already closed, in which case it's not a sockets
problem, but an application problem.
files:
 Doc/howto/sockets.rst | 6 ------
 1 files changed, 0 insertions(+), 6 deletions(-)

diff --git a/Doc/howto/sockets.rst b/Doc/howto/sockets.rst
--- a/Doc/howto/sockets.rst
+++ b/Doc/howto/sockets.rst
@@ -371,12 +371,6 @@
 potential_writers list. If it shows up in the writable list, you have a decent
 chance that it has connected.
 
-One very nasty problem with ``select``: if somewhere in those input lists of
-sockets is one which has died a nasty death, the ``select`` will fail. You then
-need to loop through every single damn socket in all those lists and do a
-``select([sock],[],[],0)`` until you find the bad one. That timeout of 0 means
-it won't take long, but it's ugly.
-
 Actually, ``select`` can be handy even with blocking sockets. It's one way of
 determining whether you will block - the socket returns as readable when there's
 something in the buffers. However, this still doesn't help with the problem of
-- 
Repository URL: http://hg.python.org/cpython
