➜

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 j1m
Recipients gvanrossum, j1m, vstinner, yselivanov
Date 2016-07-09.18:40:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content 
We need an executive (Guido) decision on the name of the new API. Yury wants wrap_socket.

I don't like wrap_socket because:

- It implies that it's for wrapping client and server sockets.
  (It shouldn't be for wrapping client sockets because TOOWTDI
   and create_connection.)

- I prefer names that are about goal rather than mechanism.

But I can live with anything.

I'll defer to Yury unless Guido voices an opinion.
History
Date User Action Args
2016-07-09 18:40:28j1msetrecipients: + j1m, gvanrossum, vstinner, yselivanov
2016-07-09 18:40:28j1msetmessageid: <[email protected]>
2016-07-09 18:40:28j1mlinkissue27392 messages
2016-07-09 18:40:28j1mcreate