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 maxking
Recipients barry, maxking, r.david.murray
Date 2018-03-01.05:44:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1519883058.82.0.467229070634.issue32975@psf.upfronthosting.co.za>
In-reply-to
Content
Since Python 3.6 the new EmailMessage API seems to be the default but mailbox.Message still subclasses from the old email.message.Message API.

It would be nice to get EmailMessage from mailbox so that one can rely on the new methods and content managers. Also, while it is possible to  pass a constructor to mailbox.mbox to get the new EmailMessage style message, it is different from mailbox.Message which has some extra methods.
History
Date User Action Args
2018-03-01 05:44:18maxkingsetrecipients: + maxking, barry, r.david.murray
2018-03-01 05:44:18maxkingsetmessageid: <1519883058.82.0.467229070634.issue32975@psf.upfronthosting.co.za>
2018-03-01 05:44:18maxkinglinkissue32975 messages
2018-03-01 05:44:18maxkingcreate