[issue13928] bug in asyncore.dispatcher_with_send

[adamhj]

adamhj <adamhm at gmail.com> added the comment:

ah just ignore my previous msg as i post it without seeing yours.

> Nope. It means that *before* showing up the socket was *not* connected.
ok, i read more in the asyncore source and finally understand what do you mean by "A non connected socket must be writable in order to connect". i think this is a little confusing if without any explaining, shouldn't this be written into the asyncore reference page as both readable() and writable() may be override by user?

> Of course it does: you're not connected yet (10057 = WSAENOTCONN). 
> You're supposed to use send() in handle_connect(), when the connection has already been established.
> This:
>
>     self.connect()
>     self.send('hello')
>
> ...is not asyncore is supposed to be used.

oh it seems i forgot handle_connect(), thank you for your patient explanation and sorry to have troubled you. i think there is no problem anymore

----------
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13928>
_______________________________________