➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients christian.heimes, martin.panter, r.david.murray
Date 2016-09-18.01:28:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1474162121.29.0.0619870297991.issue28134@psf.upfronthosting.co.za>
In-reply-to
Content 
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?
History
Date User Action Args
2016-09-18 01:28:41martin.pantersetrecipients: + martin.panter, christian.heimes, r.david.murray
2016-09-18 01:28:41martin.pantersetmessageid: <1474162121.29.0.0619870297991.issue28134@psf.upfronthosting.co.za>
2016-09-18 01:28:41martin.panterlinkissue28134 messages
2016-09-18 01:28:40martin.pantercreate