Artyom Gavrichenkov added the comment:
Hi Charles-François,
I've attached an update for the previous patch. Now there's no more overloading
for the third argument and socket.getsockopt accepts one more optional argument
-- a buffer to use as an input to kernel.
I can provide a man
Changes by Artyom Gavrichenkov :
--
nosy: +pitrou
___
Python tracker
<http://bugs.python.org/issue13045>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Artyom Gavrichenkov :
--
nosy: +neologix
___
Python tracker
<http://bugs.python.org/issue13045>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Artyom Gavrichenkov :
--
nosy: +python-dev
___
Python tracker
<http://bugs.python.org/issue13045>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Artyom Gavrichenkov :
--
title: [PATCH] socket.getsockopt may require custom buffer contents ->
socket.getsockopt may require custom buffer contents
___
Python tracker
<http://bugs.python.org/issu
New submission from Artyom Gavrichenkov :
Currently the Python implementation of socket.getsockopt allows only option
name, level name and buffer size as its arguments. However, IEEE Standard
1003.1-2008 allows one further argument -- an actual buffer to modify at the
kernel level. POSIX does
