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 pitrou
Recipients Andrew.Grover, baikie, brian, exarkun, giampaolo.rodola, jackdied, neologix, pitrou, rosslagerwall, synapse, therve, vstinner, wiml
Date 2011-06-05.11:21:20
SpamBayes Score 4.37393e-10
Marked as misclassified No
Message-id <1307272877.3540.0.camel@localhost.localdomain>
In-reply-to <>
> > What needs to happen to get recvmsg() supported in Python?
> Well, I guess that the only reason is that no committer is motivated
> enough to bring this into Python: it's a rather large patch, and
> honestly, I'm not sure that many people are going to use it.
> The feature I personally like the most about sendmsg/recvmsg is the
> ability to do scatter-gather I/O, but if the performance is critical,
> then I won't be using Python.
> I know that sendmsg also has some other advantages (passing FDs,
> ancillary data...).

Modules/_multiprocessing already has code using sendmsg/recvmsg,
precisely to pass FDs IIRC.
Generic support for sendmsg() and recvmsg() in the socket module would
allow to rewrite that code in pure Python.
Date User Action Args
2011-06-05 11:21:21pitrousetrecipients: + pitrou, exarkun, therve, vstinner, jackdied, baikie, giampaolo.rodola, synapse, Andrew.Grover, wiml, neologix, rosslagerwall, brian
2011-06-05 11:21:20pitroulinkissue6560 messages
2011-06-05 11:21:20pitroucreate