Ma Lin <malin...@163.com> added the comment: 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? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32394> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
