[issue13045] socket.getsockopt may require custom buffer contents

Charles-François Natali added the comment: > 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. Remarks: """ + length. If *buffer* is abs

[issue13045] socket.getsockopt may require custom buffer contents

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 manual sample

[issue13045] socket.getsockopt may require custom buffer contents

Charles-François Natali added the comment: Hello, method:: socket.getsockopt(level, optname[, optarg]) The overloading of the third parameter is confusing: it can already be an integer value or a buffer size, I don't think that adding a third possibility is a good idea. It might be better to

[issue13045] socket.getsockopt may require custom buffer contents

Changes by Artyom Gavrichenkov : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue13045] socket.getsockopt may require custom buffer contents

Changes by Artyom Gavrichenkov : -- nosy: +neologix ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue13045] socket.getsockopt may require custom buffer contents

Changes by Artyom Gavrichenkov : -- nosy: +python-dev ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue13045] socket.getsockopt may require custom buffer contents

Changes by Artyom Gavrichenkov : -- title: [PATCH] socket.getsockopt may require custom buffer contents -> socket.getsockopt may require custom buffer contents ___ Python tracker __