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 josiahcarlson
Recipients MrJean1, alanmcintyre, benjamin.peterson, donmez, facundobatista, giampaolo.rodola, josiahcarlson, mark.dickinson, ned.deily, r.david.murray
Date 2009-06-04.18:01:49
SpamBayes Score 0.0057732644
Marked as misclassified No
Message-id <1244138512.43.0.837825847704.issue5798@psf.upfronthosting.co.za>
In-reply-to
Content
I installed 3.1rc1 on my OS X (10.5.?) machine, updated asynchat, and ran 
the test with and without my change.  Without my change, it breaks in the 
way described numerous times.  With my change, it seems to work fine on OS 
X, linux, and Windows for me.

Looking at line 106 in py3k/Lib/asyncore.py 
(http://svn.python.org/view/python/branches/py3k/Lib/asyncore.py?
annotate=73183) gets me "obj.handle_close()".  Your tracebacks show line 
106 calling "obj.handle_expt_event()", which is the old code.
History
Date User Action Args
2009-06-04 18:01:53josiahcarlsonsetrecipients: + josiahcarlson, facundobatista, mark.dickinson, alanmcintyre, giampaolo.rodola, donmez, MrJean1, benjamin.peterson, ned.deily, r.david.murray
2009-06-04 18:01:52josiahcarlsonsetmessageid: <1244138512.43.0.837825847704.issue5798@psf.upfronthosting.co.za>
2009-06-04 18:01:50josiahcarlsonlinkissue5798 messages
2009-06-04 18:01:49josiahcarlsoncreate