Message137688
| 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.3739296e-10 |
| Marked as misclassified |
No |
| Message-id |
<1307272877.3540.0.camel@localhost.localdomain> |
| In-reply-to |
<BANLkTimFzrUXGCU=wMCTUA0ad69w84Tv8g@mail.gmail.com> |
| Content |
> > 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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年06月05日 11:21:21 | pitrou | set | recipients:
+ pitrou, exarkun, therve, vstinner, jackdied, baikie, giampaolo.rodola, synapse, Andrew.Grover, wiml, neologix, rosslagerwall, brian |
| 2011年06月05日 11:21:20 | pitrou | link | issue6560 messages |
| 2011年06月05日 11:21:20 | pitrou | create |
|