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 pitrou
Recipients BreamoreBoy, gearb0x, jnoller, neologix, news1234, pitrou
Date 2012-01-03.17:04:29
SpamBayes Score 0.00043748494
Marked as misclassified No
Message-id <1325610269.85.0.498899743552.issue8184@psf.upfronthosting.co.za>
In-reply-to
Content
There's a length MSDN article about this:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms740621%28v=vs.85%29.aspx

Executive summary: it's a can of worms.

However, let me point out the following sentence:
“Ports without SO_EXCLUSIVEADDRUSE set may be reused as soon as the socket on which bind was previously called is closed.”

...which seems to suggest we shouldn't use SO_REUSEADDR under Windows, since Windows sockets appear to have the Unix SO_REUSEADDR semantics by default.
History
Date User Action Args
2012-01-03 17:04:29pitrousetrecipients: + pitrou, jnoller, news1234, neologix, BreamoreBoy, gearb0x
2012-01-03 17:04:29pitrousetmessageid: <1325610269.85.0.498899743552.issue8184@psf.upfronthosting.co.za>
2012-01-03 17:04:29pitroulinkissue8184 messages
2012-01-03 17:04:29pitroucreate