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 neologix
Recipients Andrew.Grover, baikie, brian, exarkun, giampaolo.rodola, jackdied, neologix, pitrou, rosslagerwall, synapse, therve, vstinner, wiml
Date 2011-05-31.17:57:59
SpamBayes Score 5.94724e-12
Marked as misclassified No
Message-id <>
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...).

> recvmsg() is required to get get transparent UDP proxies working under Linux
> using tproxy, the code needs to run recvmsg() to be able to find out what the
> original destination address was for the the packet.

Sounds like a job for raw sockets, no? (well, you need CAP_NET_RAW)

In short, I think that you just need to find a core developer
interested, I personally am not (but I'm not opposed to it either :-).
Date User Action Args
2011-05-31 17:58:00neologixsetrecipients: + neologix, exarkun, pitrou, therve, vstinner, jackdied, baikie, giampaolo.rodola, synapse, Andrew.Grover, wiml, rosslagerwall, brian
2011-05-31 17:58:00neologixlinkissue6560 messages
2011-05-31 17:57:59neologixcreate