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 Daniel.Evers
Recipients Daniel.Evers, exarkun, neologix, tarek
Date 2010-04-22.20:01:59
SpamBayes Score 1.36272e-08
Marked as misclassified No
Message-id <1271966524.61.0.5942977062.issue8498@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for your help. I'll close the listen socket.

Nevertheless I'd like to understand the check in sock_listen. The commit message is not very helpful, I agree, that's why I wrote this issue. 0 is a valid value, and I'd suggest two ways to handle this situation:
1. Always set backlog at least to 1 (like now), but make this explicit in the documentation (docs.python.org says "should be at least 1" which is not the same as "will be at least 1")
2. Allow backlog = 0 and make a note in the docs that the exact behaviour will be implementation/OS-specific.

In case (1) the hint to close the listen socket should also be added to the documentation.
History
Date User Action Args
2010-04-22 20:02:05Daniel.Everssetrecipients: + Daniel.Evers, exarkun, tarek, neologix
2010-04-22 20:02:04Daniel.Everssetmessageid: <1271966524.61.0.5942977062.issue8498@psf.upfronthosting.co.za>
2010-04-22 20:02:01Daniel.Everslinkissue8498 messages
2010-04-22 20:01:59Daniel.Everscreate