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 malin
Recipients malin, ned.deily, paul.moore, skn78, steve.dower, thatiparthy, tim.golden, tjguk, zach.ware
Date 2018-02-01.10:04:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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?
I'm not a socket expert, I have a question about the former one.

Imagine someone changed those values in his/her code, for example:
socket.TCP_KEEPCNT = 20

His/her code works fine on new version Windows. Will this line break things again on old version Windows?
Date User Action Args
2018-02-01 10:04:22malinsetrecipients: + malin, paul.moore, tim.golden, ned.deily, zach.ware, steve.dower, thatiparthy, tjguk, skn78
2018-02-01 10:04:22malinsetmessageid: <>
2018-02-01 10:04:22malinlinkissue32394 messages
2018-02-01 10:04:22malincreate