[issue6560] socket sendmsg(), recvmsg() methods
Brian May
report at bugs.python.org
Mon Jun 6 01:35:26 CEST 2011
Brian May <brian at microcomaustralia.com.au> added the comment:
To address some of the comments above:
* Yes, the patch is large. However, most of this is in the tests. Only A relatively small part is in the code that implements the required functionality. I don't care much myself about the test cases, however would have assumed these would help get it into upstream.
(baikie-hwundram-v5-hg.diff)
Doc/library/socket.rst | 176 +++
Lib/ssl.py | 24
Lib/test/test_socket.py | 2120 ++++++++++++++++++++++++++++++++++++++++++++++++
Lib/test/test_ssl.py | 13
Modules/socketmodule.c | 809 ++++++++++++++++++
5 files changed, 3142 insertions(+)
* raw sockets are inappropriate for using UDP TPROXY support. I don't want to bypass the kernel code and have to pass headers etc myself, I just want to get the destination address so I know where the packet was original destined for. recvmsg() is the correct solution.
* Thanks for the 2.x patch. Will try that out now.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue6560>
_______________________________________
More information about the Python-bugs-list
mailing list