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 Daniel Black
Recipients Daniel Black, barry, r.david.murray
Date 2019-03-28.05:03:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1553749395.69.0.447008656018.issue36460@roundup.psfhosted.org>
In-reply-to
Content
AMP is being adopted by Gmail, Outlook, Mail.ru and Yahoo! as a valid MIME content-type message part. The Python email module could support this, I believe in an RFC-compliant way within the mimetypes module at mimetypes.types_map (and elsewhere as needed, possibly in the parser and generator though I suspect not as it's really utf-8 html other than the kinda silly lightning bolt emoji, which is optional to the AMP spec). My current concern is that the types map dictionary is keyed on filename extensions but AMP MIME (text/x-amp-html) is also .html. We can't have two keys for this and AMP doesn't have its own filename extension.
History
Date User Action Args
2019-03-28 05:03:15Daniel Blacksetrecipients: + Daniel Black, barry, r.david.murray
2019-03-28 05:03:15Daniel Blacksetmessageid: <1553749395.69.0.447008656018.issue36460@roundup.psfhosted.org>
2019-03-28 05:03:15Daniel Blacklinkissue36460 messages
2019-03-28 05:03:15Daniel Blackcreate