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 methane
Recipients asvetlov, malin, methane, ned.deily, njs, paul.moore, skn78, steve.dower, thatiparthy, tim.golden, tjguk, zach.ware
Date 2018-02-05.04:11:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> On Linux/Unix, the compile-time headers always consist with the system, so there should not has this problem.
> Correct me if I'm wrong.

No.  Compile-time and run-time system is not always consist.
Kernel version may be upgraded / downgraded after Python is built.
And header version may not be consistent with kernel version.

There are some cases that system may return error for unsupported setsockopt() on Linux.

So I think websocket-client should catch OSError for setsockopt.

But if there are many broken libraries in the world, it's considerable
that hide it on Python side.

Kamil said "This behavior breaks many libraries that i use."
But I saw only websocket-client.  How many other libraries?
Date User Action Args
2018-02-05 04:11:33methanesetrecipients: + methane, paul.moore, tim.golden, ned.deily, njs, asvetlov, zach.ware, steve.dower, thatiparthy, malin, tjguk, skn78
2018-02-05 04:11:33methanesetmessageid: <>
2018-02-05 04:11:33methanelinkissue32394 messages
2018-02-05 04:11:33methanecreate