➜

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 njs
Recipients aeros, asvetlov, dacut, gvanrossum, ned.deily, njs, pitrou, vaizki, yselivanov
Date 2019-11-21.09:00:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1574326839.57.0.959133956371.issue37228@roundup.psfhosted.org>
In-reply-to
Content 
I was assuming we'd only do this on Linux, since that's where the bug is... though now that you mention it the Windows behavior is probably wonky too.

SO_REUSEADDR and SO_REUSEPORT have different semantics on all three of Windows/BSD/Linux. A higher-level interface like asyncio doesn't necessarily want to map its kwargs directly to non-portable low-level options like this.
History
Date User Action Args
2019-11-21 09:00:39njssetrecipients: + njs, gvanrossum, pitrou, ned.deily, asvetlov, yselivanov, dacut, vaizki, aeros
2019-11-21 09:00:39njssetmessageid: <1574326839.57.0.959133956371.issue37228@roundup.psfhosted.org>
2019-11-21 09:00:39njslinkissue37228 messages
2019-11-21 09:00:39njscreate