[Python-bugs-list] [ python-Bugs-817920 ] select behavior undefined for empty lists

SourceForge.net noreply at sourceforge.net
Sun Oct 5 23:55:57 EDT 2003


Bugs item #817920, was opened at 2003-10-05 00:08
Message generated for change (Comment added) made by jhylton
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=817920&group_id=5470

Category: Python Library
Group: None
Status: Open
Resolution: None
>Priority: 3
Submitted By: Vaclav Dvorak (vdvo)
Assigned to: Nobody/Anonymous (nobody)
Summary: select behavior undefined for empty lists

Initial Comment:
<nit-picking>

The manual for select.select() says:

"Empty lists are allowed, but acceptance of three empty

lists is platform-dependent. (It is known to work on

Unix but not on Windows.)"



I believe that one of the advantages of high-level

languages is that they (are supposed to) shield the

programmer from platform specifics where possible.

Surely it can't be a problem for the select() wrapper

to have defined, platform-independent behaviour for

three empty lists?

</nit-picking>

----------------------------------------------------------------------

>Comment By: Jeremy Hylton (jhylton)
Date: 2003-10-06 03:55

Message:
Logged In: YES 
user_id=31392

Like he said, please provide a patch.



----------------------------------------------------------------------

Comment By: Itamar Shtull-Trauring (itamar)
Date: 2003-10-05 16:57

Message:
Logged In: YES 
user_id=32065

Both asyncore and Twisted have code to deal with this

Windows issue, so most people never encounter it. A fix

(doing a sleep in the C code, essentially) would be nice,

but I suspect no one will bother unless you attach a patch.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=817920&group_id=5470



More information about the Python-bugs-list mailing list