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 njs
Recipients YoSTEALTH, christian.heimes, martin.panter, njs, pitrou, r.david.murray, vstinner, yselivanov
Date 2018-12-29.06:10:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Am I right that this is considered fixed (or at least as fixed as it can be), and the issue should be closed?

Also, small note in case anyone stumbles across this in the future and is confused: Python does *not* handle this correctly on Windows. I suspect Christian was confused because there's an undocumented features on Windows where if you pass fileno=<opaque string returned by socket.share()>, then that correctly reinstantiates the socket object. But fileno=<raw socket handle> doesn't seem to do any special autodetection of type/family/proto.
Date User Action Args
2018-12-29 06:10:50njssetrecipients: + njs, pitrou, vstinner, christian.heimes, r.david.murray, martin.panter, yselivanov, YoSTEALTH
2018-12-29 06:10:49njssetmessageid: <>
2018-12-29 06:10:49njslinkissue28134 messages
2018-12-29 06:10:49njscreate