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 r.david.murray
Recipients barry, lpolzer, r.david.murray, richard, vstinner
Date 2013-11-20.16:06:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384963593.51.0.151257606834.issue19662@psf.upfronthosting.co.za>
In-reply-to
Content
I think the only backward compatible solution is to add a switch of *some* sort (exact API TBD), whose default is to continue to decode using utf-8, and document it as wrong.

Conversion of an email to unicode should be handled by the email package, not by smtpd, which is why I say smtpd should be emitting binary.

As I say, I need to find time to look at the current API in more detail before I'll be comfortable discussing the new API.  I've put it on my list, but likely I won't get to it until the weekend.
History
Date User Action Args
2013-11-20 16:06:33r.david.murraysetrecipients: + r.david.murray, barry, richard, vstinner, lpolzer
2013-11-20 16:06:33r.david.murraysetmessageid: <1384963593.51.0.151257606834.issue19662@psf.upfronthosting.co.za>
2013-11-20 16:06:33r.david.murraylinkissue19662 messages
2013-11-20 16:06:33r.david.murraycreate