This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: select behavior undefined for empty lists
Type: Stage:
Components: Library (Lib) Versions:
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: draghuram, itamar, jhylton, vdvo
Priority: low Keywords:

Created on 2003-10-05 00:08 by vdvo, last changed 2022-04-10 16:11 by admin. This issue is now closed.

Messages (4)
msg18546 - (view) Author: Vaclav Dvorak (vdvo) Date: 2003-10-05 00:08
<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>
msg18547 - (view) Author: Itamar Shtull-Trauring (itamar) Date: 2003-10-05 16:57
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.
msg18548 - (view) Author: Jeremy Hylton (jhylton) (Python triager) Date: 2003-10-06 03:55
Logged In: YES 
user_id=31392

Like he said, please provide a patch.
msg61644 - (view) Author: Raghuram Devarakonda (draghuram) (Python triager) Date: 2008-01-24 17:47
no activity. closing it.
History
Date User Action Args
2022-04-10 16:11:36adminsetgithub: 39369
2008-01-24 17:47:35draghuramsetstatus: open -> closed
nosy: + draghuram
resolution: wont fix
messages: + msg61644
2003-10-05 00:08:20vdvocreate