[issue27397] email.message.Message.get_payload(decode=True) raises AssertionError that "should never happen"
Jami Lindh
report at bugs.python.org
Fri Jul 29 02:33:37 EDT 2016
Jami Lindh added the comment:
It might also make sense to return the payload undecoded. The documentation for get_payload() function says:
"[...] the payload will be decoded if this header’s value is quoted-printable or base64. If some other encoding is used, or Content-Transfer-Encoding header is missing, the payload is returned as-is (undecoded)."
Even though the header's value tries to convince you "base64" is the encoding, it is - in this case - either broken base64 or not. Hence it might fall into the category "some other encoding is used", justifying the "payload is returned as-is (undecoded)".
As to the original payload Claudiu posted, in that the mailserver has truncated the email. This already provides the user with non-base64 string that they try to convince you to decode as base64. My argument is still valid in this case.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue27397>
_______________________________________
More information about the Python-bugs-list
mailing list