Author giampaolo.rodola
Recipients Manjusaka, giampaolo.rodola, neologix, vstinner, yselivanov
Date 2018-12-17.11:34:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1545046469.33.0.788709270274.issue35517@psf.upfronthosting.co.za>
In-reply-to
Content
I see. Then I would say it's a matter of deciding what's the best API to provide. Another possibility is to promote the underlying epoll() instance as a public property, so one can do:

>>> s = selectors.EpollSelector()
>>> s.register(fd, EVENT_READ)
>>> s.selector.modify(fd, select.EPOLLEXCLUSIVE)

That raises the question whether all selector classes should have a public "selector" attribute. poll() and devpoll() related classes may need it for POLLPRI, POLLRDHUP, POLLWRBAND or others (whatever their use case is). kqueue() also has it's own specific constants (KQ_FILTER_* and KQ_EV_*). The only one where a public "selector" property would be useless is SelectSelector.
History
Date User Action Args
2018-12-17 11:34:29giampaolo.rodolasetrecipients: + giampaolo.rodola, vstinner, neologix, yselivanov, Manjusaka
2018-12-17 11:34:29giampaolo.rodolasetmessageid: <1545046469.33.0.788709270274.issue35517@psf.upfronthosting.co.za>
2018-12-17 11:34:29giampaolo.rodolalinkissue35517 messages
2018-12-17 11:34:29giampaolo.rodolacreate