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 steve.dower
Recipients ned.deily, paul.moore, skn78, steve.dower, thatiparthy, tim.golden, tjguk, zach.ware
Date 2017-12-21.21:13:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Okay, so it looks like we don't have any prior art to conditionally omit constants from _socket based on OS level, and nothing in the setsockopt() doc suggests that it may fail like this.

So we either need to explicitly exclude this symbol on Windows (at least until we drop support for pre-Windows 10 versions) or silently ignore setsockopt errors for future good arguments. I'm inclined to do the former - other opinions?
Date User Action Args
2017-12-21 21:13:20steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, ned.deily, zach.ware, thatiparthy, tjguk, skn78
2017-12-21 21:13:20steve.dowersetmessageid: <>
2017-12-21 21:13:20steve.dowerlinkissue32394 messages
2017-12-21 21:13:20steve.dowercreate