[issue29332] Uniform SelectSelector._select behavior

2017-01-20 Thread Wen Adam
Wen Adam added the comment: I know it works on python3.4, but black magic still exists in selectors lib，and 3rd-party module have to prepare two function to make compatibility. -- ___ Python tracker __

[issue29332] Uniform SelectSelector._select behavior

2017-01-20 Thread Berker Peksag
Berker Peksag added the comment: Great! Since this is no longer an issue on Python 3.4+, I'm going to close this as a duplicate of issue 27634 and merge https://github.com/berkerpeksag/selectors34/pull/4. -- resolution: -> duplicate stage: -> resolved status: open -> closed supersede

[issue29332] Uniform SelectSelector._select behavior

2017-01-20 Thread Wen Adam
Wen Adam added the comment: Thx for your replying, Peksag. I encountered this problem is really because of Gevent and Selector34. Gevent fixed this issue but only works for python3.4+(https://github.com/gevent/gevent/blob/master/src/gevent/monkey.py#L497) by a tricking way. python 2.x still h

[issue29332] Uniform SelectSelector._select behavior

2017-01-20 Thread Berker Peksag
Berker Peksag added the comment: Thanks for the report! This is a duplicate of issue 27634. Since we got multiple reports [1][2] about the same problem on selectors34 (backport of selector module) and use of Gevent is very popular, I think we should reconsider the idea of wrapping select.selec

[issue29332] Uniform SelectSelector._select behavior

2017-01-20 Thread Wen Adam
New submission from Wen Adam: SelectSelector._select is differently on different platforms. On win32, SelectSelector._select is a unbound/bound method and pass instance as the first argument, but on *nix, SelectSelector._select is a builtin_function_or_method(Although self.select still works)