Hello!

asyncore.dispatcher_with_send undocumented in all python versions

Feel like writing some documentation?

Ok, I'll try :). I'll send it today or tomorrow.

This is my explanation of dispatcher_with_send. As my english is far from 
perfect and I'm not expirienced writing documentation you need to review 
it and fix my mistakes.


class asyncore.dispatcher_with_send

This is class based on asyncore.dispatcher. The only difference that 
unlike dispatcher.send which is direct mean to the socket.send() send() 
of this class uses buffered io. At first all outgoing data saved to the 
buffer and later it will send when socket becomes avaliable for write. 
Thus dispatcher_with_send.send() will never return EWOULDBLOCK error. 
Also you shuldn't overrdie writable() method as in this dispatcher it 
will automatically return convient value depending weither output buffer 
empty or not.

Please don't keep this bug open :(

Oh, we sometimes keep bugs open for years around here, until someone
finds time to deal with them.  It's our collective memory...thanks for
taking a crack at the wording.  If you feel like turning it into a patch
against the documentation (which is in the Doc directory of a CVS
checkout, see http://www.python.org/dev for more info on how to generate
a patch), someone might get to it sooner.

I documented this some months ago:
http://docs.python.org/library/asyncore.html#asyncore.dispatcher_with_send
Being asynchat's push() method more convenient for such kind of task I expressively avoided to be too specific about dispatcher_with_send.