[issue18044] Email headers do not properly decode to unicode.

2013-07-11 Thread Roundup Robot
Roundup Robot added the comment: New changeset 4acb822f4c43 by R David Murray in branch '3.3': #18044: Fix parsing of encoded words of the form =?utf8?q?=XX...?= http://hg.python.org/cpython/rev/4acb822f4c43 New changeset 32c6cfffbddd by R David Murray in branch 'default': Merge: #18044: Fix

[issue18044] Email headers do not properly decode to unicode.

2013-07-11 Thread R. David Murray
R. David Murray added the comment: This is actually two separate bugs, both a bit embarrassing. The first one (that I just fixed) is that when parsing an encoded word I was only checking for decimal digits after an '=' (instead of the correct hex digits) when trying to do robust detection of

[issue18044] Email headers do not properly decode to unicode.

2013-07-11 Thread R. David Murray
R. David Murray added the comment: The issue for the second bug is issue 18431. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18044 ___ ___

[issue18044] Email headers do not properly decode to unicode.

2013-05-26 Thread Ezio Melotti
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue18044 ___ ___

[issue18044] Email headers do not properly decode to unicode.

2013-05-23 Thread Tim Rawlinson
New submission from Tim Rawlinson: In Python 3.3 decoding of headers to unicode is supposed to be automatic but fails in several cases, including one shown as successful in the documentation: msg = message_from_string('Subject: =?utf-8?q?=C3=89ric?=\n\n', policy=default)