Message270059
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. |
|
Date |
User |
Action |
Args |
2016-07-09 18:40:28 | j1m | set | recipients:
+ j1m, gvanrossum, vstinner, yselivanov |
2016-07-09 18:40:28 | j1m | set | messageid: <1468089628.78.0.345703144875.issue27392@psf.upfronthosting.co.za> |
2016-07-09 18:40:28 | j1m | link | issue27392 messages |
2016-07-09 18:40:28 | j1m | create | |
|