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 yselivanov
Recipients gvanrossum, j1m, vstinner, yselivanov
Date 2016-07-09.18:40:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> wrap_socket implies that it's for wrapping client or server sockets, but it's not. It's only for handling server sockets. Also, I prefer a name that reflects goal, not mechanism.

> I think the name should be discussed over here:

Why can't `wrap_socket` be used for wrapping client sockets?  I think we can refactor asyncio to use it in 'create_connection', and maybe to accept new connections.

To my ear, 'asyncio.handle_connection' implies that asyncio will "handle" the connection, i.e. that asyncio itself would do more than just wrapping the socket and attaching a protocol instance.
Date User Action Args
2016-07-09 18:40:43yselivanovsetrecipients: + yselivanov, gvanrossum, vstinner, j1m
2016-07-09 18:40:43yselivanovsetmessageid: <>
2016-07-09 18:40:43yselivanovlinkissue27392 messages
2016-07-09 18:40:43yselivanovcreate