asynchat - operation could not complete w/ blocking

Andreas R. andreas at
Wed Mar 8 10:16:19 CET 2006

Dennis Lee Bieber wrote:
> On Wed, 08 Mar 2006 08:57:53 +0100, "Andreas R."
> <andreas at> declaimed the following in
> comp.lang.python:
>> The problem I was having with push, is that is does not always send 
>> complete packages.
>> The solution to this was to use sendall() instead, but sendall() gives 
>> blocking error messages.
> 	Somehow, the above seems logical... "push" probably doesn't "send
> complete packages" because doing so would require blocking; instead it
> sends what won't block, presuming "you" (the programmer) will code
> whatever is needed to handle partial sends and put the rest out on a
> later "push".
> 	"sendall" may be sending everything, but it does so by blocking
> until the other end acknowledges enough packets have been received to
> ensure that no data is lost.

Yes, this is how I understood sendall. But why does it sometimes report 
the error: (10035, 'The socket operation could not complete without 

- Andreas

More information about the Python-list mailing list