[issue26666] File object hook to modify select(ors) event mask

Andrew Svetlov added the comment: Out of asynio library scope. -- nosy: +asvetlov resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue26666] File object hook to modify select(ors) event mask

STINNER Victor added the comment: > The whole point of a transparent SOCKS module is that it provides a function > that's a *drop-in replacement* for socket.socket(). Fully transparent asynchronous I/O is an old dream of developers. You may try eventlet if you like monkey-patching. It's a del

[issue26666] File object hook to modify select(ors) event mask

Martin Panter added the comment: Python’s select() call operates at a minimal OS level. I don’t completely understand your __preselect__() etc proposal, but it does sound like you are trying to invent another higher-level “asynchronous” framework like asyncio. I think you are wrong about the p

[issue26666] File object hook to modify select(ors) event mask

Zack Weinberg added the comment: > Obvious question: why not working on the asyncio support in this library? The whole point of a transparent SOCKS module is that it provides a function that's a *drop-in replacement* for socket.socket(). An asyncio-based SOCKS module would have a completely d

[issue26666] File object hook to modify select(ors) event mask

STINNER Victor added the comment: > I'm attempting to enhance a transparent-SOCKS module > (https://github.com/Anorov/PySocks) to support non-blocking connect(). Obvious question: why not working on the asyncio support in this library? -- components: +asyncio nosy: +gvanrossum, haypo,

[issue26666] File object hook to modify select(ors) event mask

New submission from Zack Weinberg: This is pretty esoteric, please bear with me. I'm attempting to enhance a transparent-SOCKS module (https://github.com/Anorov/PySocks) to support non-blocking connect(). This means, you should be able to do this: socks.set_default_proxy(socks.SOCKS5, "l