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 neologix
Recipients Daniel.Evers, exarkun, neologix, tarek
Date 2010-04-22.12:00:27
SpamBayes Score 8.32205e-05
Marked as misclassified No
Message-id <>
That's a non-portable user of listen()'s backlog, see
A backlog argument of 0 may allow the socket to accept connections, in which case the length of the listen queue may be set to an implementation-defined minimum value.

Furthermore, python's socket documentation makes it clear:
Enable a server to accept connections.  The backlog argument must be at least 1; it specifies the number of unaccepted connection that the system will allow before refusing new connections.

If you really want to only accept 1 connection (I'm talking of sending back a SYN-ACK, not an accept() call), you can just close the server socket as soon as you've done the accept, and re-open it when you're ready to process another request. Or you could accept new connections and close them immediately (but then you'd send back a SYN-ACK then a FIN).

So I'd say it's not a python bug.
Date User Action Args
2010-04-22 12:00:32neologixsetrecipients: + neologix, exarkun, tarek, Daniel.Evers
2010-04-22 12:00:31neologixsetmessageid: <>
2010-04-22 12:00:30neologixlinkissue8498 messages
2010-04-22 12:00:27neologixcreate