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 neologix
Date 2013-01-06.00:33:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357432404.49.0.731162769858.issue16873@psf.upfronthosting.co.za>
In-reply-to
Content
In issue #16853, it was noted that many several projects don't set epoll.poll() maxevents argument, which effectively limits the number of events retuend to FD_SETSIZE-1 (set in selectmodule.c).

Also, the methode documentation can confuse users into thinking that by default, the number of events is unlimited:
"""

.. method:: epoll.poll(timeout=-1, maxevents=-1)

   Wait for events. timeout in seconds (float)
"""

It would probably make sense to use a larger default value for epoll max events (the only downside is increased memory consumption for the events array), maybe based on RLIMIT_NOFILE hard limit.
And the documentation should probably be improved.
History
Date User Action Args
2013-01-06 00:33:24neologixsetrecipients: + neologix
2013-01-06 00:33:24neologixsetmessageid: <1357432404.49.0.731162769858.issue16873@psf.upfronthosting.co.za>
2013-01-06 00:33:24neologixlinkissue16873 messages
2013-01-06 00:33:24neologixcreate