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 vstinner
Recipients gvanrossum, martin.panter, vstinner, yselivanov, zwol
Date 2016-03-30.01:16:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1459300569.6.0.068356540761.issue26666@psf.upfronthosting.co.za>
In-reply-to
Content
> 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 deliberate choice in the asyncio design to make asynchonous I/O explicit in the code.
History
Date User Action Args
2016-03-30 01:16:09vstinnersetrecipients: + vstinner, gvanrossum, martin.panter, yselivanov, zwol
2016-03-30 01:16:09vstinnersetmessageid: <1459300569.6.0.068356540761.issue26666@psf.upfronthosting.co.za>
2016-03-30 01:16:09vstinnerlinkissue26666 messages
2016-03-30 01:16:09vstinnercreate