[issue7304] email.message.Message.set_payload and as_string given charset 'us-ascii' plus 8bit data produces invalid message
Changes by Dmitry Shachnev mity...@gmail.com: -- nosy: +mitya57 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7304 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7304] email.message.Message.set_payload and as_string given charset 'us-ascii' plus 8bit data produces invalid message
Changes by R. David Murray rdmur...@bitdance.com: -- assignee: r.david.murray - components: +email -Library (Lib) ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7304 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7304] email.message.Message.set_payload and as_string given charset 'us-ascii' plus 8bit data produces invalid message
Changes by R. David Murray rdmur...@bitdance.com: -- assignee: - r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7304 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7304] email.message.Message.set_payload and as_string given charset 'us-ascii' plus 8bit data produces invalid message
R. David Murray rdmur...@bitdance.com added the comment: In Python2 the fix would be to use charset unknown-8bit instead of us-ascii. In Python3 this actually puts unicode in the message body. There we should default to utf-8, but this requires a more extensive change than the Python2 change, and probably should not be backported. Once this is fixed in Python3 the utf-8 default check can be removed from MIMEText (issue 14380). -- versions: +Python 3.3 -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7304 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7304] email.message.Message.set_payload and as_string given charset 'us-ascii' plus 8bit data produces invalid message
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: +barry versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7304 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7304] email.message.Message.set_payload and as_string given charset 'us-ascii' plus 8bit data produces invalid message
New submission from R. David Murray rdmur...@bitdance.com: The following produces a non-conformant message, since the us-ascii charset is strictly 7bit: import email.message m = email.message.Message() m.set_payload(A few lines ... of 8-bit text ... ... One high bit character: ². ... , 'us-ascii') print m.as_string() MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit A few lines of 8-bit text One high bit character: ². -- components: Library (Lib) messages: 95133 nosy: r.david.murray priority: normal severity: normal stage: test needed status: open title: email.message.Message.set_payload and as_string given charset 'us-ascii' plus 8bit data produces invalid message type: behavior versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7304 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com