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.

Author neologix
Recipients christian.heimes, felipecruz, giampaolo.rodola, gvanrossum, meador.inge, neologix, pitrou, rosslagerwall, sbt
Date 2013-01-08.22:31:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
This should fix some kqueue failures (the FDs were not unregistered,
which could result in spurious FDs being reported at a later time).

For the "negative FDs", all spurious events are now caught and logged
(I think it's better than silently ignoring them as it is now).
Hopefully we'll see an EV_ERROR with set to a sensible errno.

The implementation should now be more or less complete, apart from the
WSAPoll, which I'm unable to add/test.

Richard, in Tulip's WSAPoll code, it reads:

    class WindowsPollPollster(PollPollster):
        """Pollster implementation using WSAPoll.

        WSAPoll is only available on Windows Vista and later.  Python
        does not currently support WSAPoll, but there is a patch
        available at

Does this means that this code need the patch from issue #16507 to work?

Also, I've read something about IOCP: is this a replacement for
WSAPoll, are there plans to get it merged at some point to python (and
if yes, would the select module be a proper home for this)?
File name Uploaded
tulip-selectors-3.diff neologix, 2013-01-08.22:31:37
Date User Action Args
2013-01-08 22:31:39neologixsetrecipients: + neologix, gvanrossum, pitrou, giampaolo.rodola, christian.heimes, meador.inge, rosslagerwall, sbt, felipecruz
2013-01-08 22:31:38neologixlinkissue16853 messages
2013-01-08 22:31:38neologixcreate