[New-bugs-announce] [issue10995] mailbox.py open() calls don't set encoding
Steffen Daode Nurpmeso
report at bugs.python.org
Mon Jan 24 15:23:46 CET 2011
New submission from Steffen Daode Nurpmeso <sdaoden at googlemail.com>:
I'm using the en_GB.UTF-8 locale and thus the entire I/O layer defaults to use UTF-8 encoding. Perfect.
The problem is that mailboxes are *not* and *never* in UTF-8, generally speaking, according to RFC mail standards!
So i suggest that mailbox.py either offers additional 'encoding="latin1"' constructor arguments or always uses "latin1" in open() calls.
This suffices to make mailbox.py usable -
i.e., the mailbox will be loaded/saved without causing encoder errors, and email.py will behave correctly according to message *content* anyway!
P.S.: i am far from being a Python(1) freak and feel a bit lost on *.python.org, so i might have blown the wrong whistles too load.
Sorry, if this is the case.
Thanks for python(1), it's damn slow and i love C and Perl. ;-)
components: Library (Lib)
title: mailbox.py open() calls don't set encoding
versions: Python 3.1
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce