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 benjamin.peterson, giampaolo.rodola, matejcik, pitrou
Date 2010-05-03.23:03:43
SpamBayes Score 0.0479443
Marked as misclassified No
Message-id <1272927825.13.0.963947746457.issue3620@psf.upfronthosting.co.za>
In-reply-to
Content
Adding this:

    def handle_error(self):
        raise

...to SimSMTPChannel class would help to provide a clearer error message to understand where exactly EBADF comes from, altough I think this was an old asyncore bug which have already been fixed.
Is this still reproducible on Python 3.2?
History
Date User Action Args
2010-05-03 23:03:45giampaolo.rodolasetrecipients: + giampaolo.rodola, pitrou, matejcik, benjamin.peterson
2010-05-03 23:03:45giampaolo.rodolasetmessageid: <1272927825.13.0.963947746457.issue3620@psf.upfronthosting.co.za>
2010-05-03 23:03:43giampaolo.rodolalinkissue3620 messages
2010-05-03 23:03:43giampaolo.rodolacreate