mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-11-11 14:44:57 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 8

Drop claim about nasty problem.

Browse source 
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.
This commit is contained in:
Martin v. Löwis 2011-06-06 10:27:56 +02:00
parent 2d449aa004
commit 8480bc65bc
1 changed files with 0 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Doc/howto/sockets.rst
View file

@ -371,12 +371,6 @@ have created a new socket to ``connect`` to someone else, put it in the
potential_writers list. If it shows up in the writable list, you have a decent potential_writers list. If it shows up in the writable list, you have a decent
chance that it has connected. 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 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 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 something in the buffers. However, this still doesn't help with the problem of