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 mark.dickinson
Recipients MrJean1, alanmcintyre, donmez, facundobatista, giampaolo.rodola, josiahcarlson, mark.dickinson, r.david.murray
Date 2009-05-07.19:28:06
SpamBayes Score 1.1740481e-05
Marked as misclassified No
Message-id <1241724487.98.0.0573518290646.issue5798@psf.upfronthosting.co.za>
In-reply-to
Content
So the sequence of events seems to be:
  asyncore.readwrite calls obj.handle_read_event
  ... which calls obj.handle_read (3rd branch of handle_read_event)
  ... which is defined in asynchat.py;  it calls obj.recv
  ... (back in asyncore now): recv calls obj.socket.recv
  ... and gets no data, so it then calls obj.handle_close
  ... which calls obj.close(), and so closes obj.socket as well.

and now obj.handle_expt_event gets confused because the socket is 
closed.

Now what?
History
Date User Action Args
2009-05-07 19:28:08mark.dickinsonsetrecipients: + mark.dickinson, facundobatista, josiahcarlson, alanmcintyre, giampaolo.rodola, donmez, MrJean1, r.david.murray
2009-05-07 19:28:07mark.dickinsonsetmessageid: <1241724487.98.0.0573518290646.issue5798@psf.upfronthosting.co.za>
2009-05-07 19:28:06mark.dickinsonlinkissue5798 messages
2009-05-07 19:28:06mark.dickinsoncreate