Martin Panter added the comment:
Personally, I’m not too enthusiastic, because it is rather magical, and does
not work in all cases. It seems more like a feature than a bug fix. But I have
rarely used the fileno=... parameter, and it shouldn’t have much negative
impact, so I’m not too fussed.
According to Issue 27377, these are some cases where parts won’t work:
* Windows and OS X (and older versions of Linux and BSD) don’t have SO_PROTOCOL
* getsockname() not guaranteed to work on unbound sockets, especially on
Windows, and Free BSD with SCTP sockets
Also, if we are going to read SO_PROTOCOL when fileno=... is given, why not
also read it in the normal case when proto=0 (unspecified) is given?
Python tracker <rep...@bugs.python.org>
Python-bugs-list mailing list