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, cjw296, r.david.murray, terry.reedy
Date 2010-08-07.15:01:59
SpamBayes Score 7.1121725e-08
Marked as misclassified No
Message-id <>
It's a plan to redesign the email API so that it can easily manipulate both bytes and strings as needed, with a backward compatibility layer that allows the current API to be used if all you need to do is process strings.  If we're lucky there may be a PyPI package that backports it to 2.x, although there the backward compatibility API will probably only work if you don't ever want to decode the message to unicode :(.

It is a project of the email-sig, but currently I'm the only one actively working on the code.

There are design documents in the wiki:

the current code (which of course is in the middle of various transformations and the docs aren't completely up to date) is on launchpad in deference to Barry:

I welcome your comments!

(*) email4 is the package in most of the actively used versions of Python2.x, email5 is the version in 3.0/3.1/3.2, email6 will hopefully be the version in 3.3.
Date User Action Args
2010-08-07 15:02:01r.david.murraysetrecipients: + r.david.murray, barry, terry.reedy, cjw296
2010-08-07 15:02:01r.david.murraysetmessageid: <>
2010-08-07 15:02:00r.david.murraylinkissue5612 messages
2010-08-07 15:01:59r.david.murraycreate