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 martin.panter, python-dev, vstinner, yselivanov
Date 2016-10-19.16:01:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476892886.99.0.762779147729.issue26685@psf.upfronthosting.co.za>
In-reply-to
Content
"After thinking about this problem for a while, I arrived to the conclusion that we need to fix asyncio."

Ah, you became reasonable :-D

"Essentially, when a user passes a socket object to the event loop API like 'create_server', they give up the control of the socket to the loop.  The loop should detach the socket object and have a full control over it."

I don't know how asyncio should be modified exactly, but I agree that someone should change in asyncio. The question is more about how to reduce headache because of the backward compatibility and don't kill performances.

Would you mind to open an issue specific for asyncio?
History
Date User Action Args
2016-10-19 16:01:27vstinnersetrecipients: + vstinner, python-dev, martin.panter, yselivanov
2016-10-19 16:01:26vstinnersetmessageid: <1476892886.99.0.762779147729.issue26685@psf.upfronthosting.co.za>
2016-10-19 16:01:26vstinnerlinkissue26685 messages
2016-10-19 16:01:26vstinnercreate