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 giampaolo.rodola
Recipients giampaolo.rodola, josiahcarlson, neologix, stutzbach, xdegaye
Date 2011-11-03.13:15:36
SpamBayes Score 0.00014848248
Marked as misclassified No
Message-id <1320326137.63.0.404914098922.issue13311@psf.upfronthosting.co.za>
In-reply-to
Content
> When the remote end disconnects, handle_close is only called if recv
> is called (from handle_read).

Actually this isn't true; handle_close() is also called in send():
http://hg.python.org/cpython/file/eb2991f7cdc8/Lib/asyncore.py#l364

I'd say your patch can be useful only in case the dispatcher subclass doesn't send() neither recv() any data, in which case the connection is supposed to remain open forever.
On one hand this might be a good thing, on the other hand I'm not sure what the repercussions might be in the existing code base out there. Probably none, but...

Perhaps you could provide more info about why you needed to do this in the first place.
Did you encounter a specific use case requiring this patch in order to work?
If so, please paste the code where you subclassed asyncore.dispatcher.
History
Date User Action Args
2011-11-03 13:15:37giampaolo.rodolasetrecipients: + giampaolo.rodola, josiahcarlson, stutzbach, neologix, xdegaye
2011-11-03 13:15:37giampaolo.rodolasetmessageid: <1320326137.63.0.404914098922.issue13311@psf.upfronthosting.co.za>
2011-11-03 13:15:37giampaolo.rodolalinkissue13311 messages
2011-11-03 13:15:36giampaolo.rodolacreate