[Stackless] Reconnection problem with stacklesssocket

Richard Tew richard.m.tew at gmail.com
Wed Aug 11 11:39:56 CEST 2010

On Wed, Aug 11, 2010 at 3:34 PM,  <stackless.nst at internike.com> wrote:
> Furthermore, from what i saw, it looks like stacklesssocket has nothing to
> do with it (sorry for being in the wrong ML afterall),

I am glad to hear it.  Thanks for reporting back and clarifying the
situation. :-)

> but it's the underlying asyncore that seem to expect blocking sockets only.
> In other words, you need to be in blocking mode to avoid blocking... ;-)

asyncore, line 238:

I do not know why you were having the problem you were having, but
simply calling setblocking should pass through to the underlying real
socket and just .. well, do something that is done anyway.

Given that people shouldn't be calling setblocking on stackless
sockets, I am not too concerned about tracking down the cause of this.
 However, really stacklesssocket if it were fully complete and stable,
should handle all proper socket usage.  But who has the time.  Anyone
want to pay me to flesh out stacklesssocket? :-)  That's about the
only way I would ever find the willpower to sit down and really polish


More information about the Stackless mailing list