[Python-checkins] peps (merge default -> default): Merge.

guido.van.rossum python-checkins at python.org
Sat Jan 5 01:06:17 CET 2013


http://hg.python.org/peps/rev/e198762fc2c0
changeset:   4652:e198762fc2c0
parent:      4650:3740f42d3b94
parent:      4651:5cff02a56194
user:        Guido van Rossum <guido at google.com>
date:        Fri Jan 04 16:06:11 2013 -0800
summary:
  Merge.

files:
  pep-3156.txt |  8 ++++++--
  1 files changed, 6 insertions(+), 2 deletions(-)


diff --git a/pep-3156.txt b/pep-3156.txt
--- a/pep-3156.txt
+++ b/pep-3156.txt
@@ -884,11 +884,15 @@
   (because to wait for a lock we'd have to use ``yield from``, which
   the ``with`` statement can't do).
 
-- Support for datagram protocols, "connected" or otherwise?  Probably
+- Support for datagram protocols, "connected" or otherwise.  Probably
   need more socket I/O methods, e.g. ``sock_sendto()`` and
   ``sock_recvfrom()``.  Or users can write their own (it's not rocket
   science).  Is it reasonable to map ``write()``, ``writelines()``,
-  ``data_received()`` to single datagrams?
+  ``data_received()`` to single datagrams?  Or should we have a
+  different ``datagram_received()`` method on datagram protocols?
+  (Glyph recommends the latter.)  And then what instead of ``write()``?
+  Finally, do we need support for unconnected datagram protocols?
+  (That would mean wrappers for ``sendto()`` and ``recvfrom()``.)
 
 - An EventEmitter in the style of NodeJS?  Or make this a separate
   PEP?  It's easy enough to do in user space, though it may benefit

-- 
Repository URL: http://hg.python.org/peps


More information about the Python-checkins mailing list