Message246779
A quick search told me that "Windows only knows the SO_REUSEADDR option, there is no SO_REUSEPORT". It should be at least documented that SO_REUSEADDR is not supported on Windows.
Maybe we should raise an exception on Windows if reuse_port=True? Ignoring the parameter is a different option, but it should be well documented that the option is ignored if socket.SO_REUSEPORT is not defined. |
|
Date |
User |
Action |
Args |
2015-07-15 22:01:25 | vstinner | set | recipients:
+ vstinner, gvanrossum, Boris.FELD, yselivanov, chris laws |
2015-07-15 22:01:25 | vstinner | set | messageid: <1436997685.37.0.729072986574.issue23972@psf.upfronthosting.co.za> |
2015-07-15 22:01:25 | vstinner | link | issue23972 messages |
2015-07-15 22:01:25 | vstinner | create | |
|