[issue20089] email.message_from_string no longer working in Python 3.4

R. David Murray added the comment: This check has been reverted in issue 20531. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed superseder: -> TypeError in e-mail.parser when non-ASCII is present type: -> behavior ___ P

[issue20089] email.message_from_string no longer working in Python 3.4

R. David Murray added the comment: Nevermind, I failed to notice the message_from_string part of the traceback. Different question: what are you doing with the message after you parse it? It is not an RFC valid message if you parse it from a string, so the only way to make it produce an RFC v

[issue20089] email.message_from_string no longer working in Python 3.4

Florian Apolloner added the comment: Yes, it works on python3.3 (from debian); I am parsing directly via email.message_from_string: Python 3.3.3 (default, Dec 8 2013, 14:51:59) [GCC 4.8.2] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import email >>> msg=

[issue20089] email.message_from_string no longer working in Python 3.4

R. David Murray added the comment: Hmm. There's definitely a backward compatibility issue here of some sort, but how are you parsing this email? And does it work or fail in some other way on 3.3 tip? -- ___ Python tracker

[issue20089] email.message_from_string no longer working in Python 3.4

Changes by Florian Apolloner : -- components: +email nosy: +barry, r.david.murray versions: +Python 3.4 ___ Python tracker ___ ___ Pyt

[issue20089] email.message_from_string no longer working in Python 3.4

New submission from Florian Apolloner: Given this email: --- Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: =?utf-8?q?Ch=C3=A8re_maman?= From: f...@example.com To: t...@example.com Date: Sat, 28 Dec 2013 13:08:07 - Message-ID: <20131228130