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 jackdied
Recipients baikie, jackdied, synapse, therve, wiml
Date 2010-02-23.23:13:45
SpamBayes Score 3.8769306e-07
Marked as misclassified No
Message-id <>
I've been digging into the patch.  Is there a reason sendmsg() wants an iterable of buffers instead of just accepting a str? The list-of-buffers more closely matches the underlying syscall but I'm not sure what the python benefit is, especially when recvmsg() only returns a single value (it only creates 1 iovec under the covers).  Python doesn't have "readv" like methods so making sendmsg/recvmsg work like recv/send (straight strings) seems like the way to go.

Also, the "y*" format character for packing/unpacking tuples is no longer supported - I'm assuming it used to mean buffers.

Does anyone have a good reference for using recvmsg/sendmsg?  I read the man pages and googled around but couldn't find anything.  I have no experience with using the calls in-the-wild.
Date User Action Args
2010-02-23 23:13:48jackdiedsetrecipients: + jackdied, therve, baikie, synapse, wiml
2010-02-23 23:13:47jackdiedsetmessageid: <>
2010-02-23 23:13:46jackdiedlinkissue6560 messages
2010-02-23 23:13:45jackdiedcreate