[issue4661] email.parser: impossible to read messages encoded in a different encoding
R. David Murray
report at bugs.python.org
Wed Sep 22 01:26:35 CEST 2010
R. David Murray <rdmurray at bitdance.com> added the comment:
The 'str' around get_param shouldn't be there, that was left over from an earlier version of the patch.
I use surrogateescape rather than latin1 because using surrogateescape with ascii encoding gives me a reliable way to know whether or not the original source was bytes containing non-ascii chars. (If it was bytes containing only ascii chars, then it doesn't matter what the original source was.)
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue4661>
_______________________________________
More information about the Python-bugs-list
mailing list