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 vaizki
Recipients aeros, asvetlov, dacut, gvanrossum, njs, pitrou, vaizki, yselivanov
Date 2019-11-20.22:49:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> We just chose an unfortunate default for one of them

I'd like to point out that it is also documented completely wrong up to this point in time and thus people who chose True are most likely to be unaware of the actual consequences. A user's explicit choice based on misinformation is not really demonstrating intent to shoot oneself in the foot.

So after changing my mind a couple of times I'm still attached to the idea that in 3.10 reuse_address and reuse_port are both removed and the tiny portion of developers who need them will just create a suitably setsockopt'd socket and pass it to the function. 2 lines of additional code is all it takes.

If the documentation had been correct all along and just the default bad, this mess would be much smaller.
Date User Action Args
2019-11-20 22:49:19vaizkisetrecipients: + vaizki, gvanrossum, pitrou, njs, asvetlov, yselivanov, dacut, aeros
2019-11-20 22:49:18vaizkisetmessageid: <>
2019-11-20 22:49:18vaizkilinkissue37228 messages
2019-11-20 22:49:18vaizkicreate