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, dmalcolm, giampaolo.rodola, josiahcarlson, matejcik, pitrou, santoso.wijaya
Date 2010-09-25.10:54:43
SpamBayes Score 1.0080974e-08
Marked as misclassified No
Message-id <1285412085.4.0.536454600811.issue6706@psf.upfronthosting.co.za>
In-reply-to
Content
> EAGAIN can be raised too. I never experienced this error condition 
> myself in pyftpdlib

From the accept() man page:

EAGAIN or EWOULDBLOCK
              The  socket  is  marked  nonblocking and no connections are present to be accepted.
              POSIX.1-2001 allows either error to be returned for this case, and does not require
              these  constants to have the same value, so a portable application should check for
              both possibilities.

> The resulting address can be None, which means that the connection 
> didn't take place.

The only way this can happen is if the accept() system call returned 0 in addrlen, which sounds rather strange. I'm not convinced hiding operating system bugs is a good idea.
History
Date User Action Args
2010-09-25 10:54:45pitrousetrecipients: + pitrou, josiahcarlson, giampaolo.rodola, matejcik, dmalcolm, santoso.wijaya, BreamoreBoy
2010-09-25 10:54:45pitrousetmessageid: <1285412085.4.0.536454600811.issue6706@psf.upfronthosting.co.za>
2010-09-25 10:54:43pitroulinkissue6706 messages
2010-09-25 10:54:43pitroucreate