R. David Murray rdmur...@bitdance.com added the comment:
This is fixed in 3.2/3.3 by the fix for issue 11492. The suggested fix for 2.7
is more radical than I'm comfortable with for a point release. I'm open to
argument on that, but in the meantime I'm closing the issue with 11492 as the
Changes by R. David Murray rdmur...@bitdance.com:
--
versions: +Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8769
___
___
Changes by R. David Murray rdmur...@bitdance.com:
--
versions: +Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8769
___
___
Changes by R. David Murray rdmur...@bitdance.com:
--
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8769
___
___
Python-bugs-list
Changes by Barry A. Warsaw ba...@python.org:
--
assignee: barry - r.david.murray
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8769
___
New submission from A.M. Kuchling li...@amk.ca:
The attached test program shows how parsing an e-mail message with the email
package, then converting the resulting message to a string, fails to round-trip
properly. Instead it breaks the encoding of the subject line.
The root of the problem:
A.M. Kuchling li...@amk.ca added the comment:
The attached patch is a possible fix; it uses the decode_header() and
make_header() functions to figure out the encoding properly; it fixes my
example, at least. But does it increase the odds of crashing on messages with
malformed headers?
A.M. Kuchling li...@amk.ca added the comment:
Minor fix to the patch: the import of Header could actually be removed, since
the class is no longer referenced at all with this change.
--
___
Python tracker rep...@bugs.python.org
