Message332038
> I don't think to make selector be a public property is a good idea. It will break the whole system integrity.
If exposing a private property is not a good idea, another choice may be construct a selector with a customized I/O multiplexer, adding an optional parameter to the __init__.
But actually I'm -1 to this change. `selectors` makes underlying implementations irrelavant to most users since we can simply use `DefaultSelector`(maybe why only read/write events are valid now?). But you are seeking to add implementation specific details back. If you know you want to add EPOLL_EXCLUSIVE, why not just use `select.epoll`? A single selector doesn't do much more than the underlying multiplexer. |
|
Date |
User |
Action |
Args |
2018-12-18 02:50:31 | xiang.zhang | set | recipients:
+ xiang.zhang, vstinner, giampaolo.rodola, neologix, yselivanov, Manjusaka |
2018-12-18 02:50:31 | xiang.zhang | set | messageid: <1545101431.08.0.788709270274.issue35517@psf.upfronthosting.co.za> |
2018-12-18 02:50:31 | xiang.zhang | link | issue35517 messages |
2018-12-18 02:50:29 | xiang.zhang | create | |
|