This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sdaoden
Recipients sdaoden
Date 2011-01-24.14:23:45
SpamBayes Score 2.383046e-10
Marked as misclassified No
Message-id <1295879026.46.0.299345130238.issue10995@psf.upfronthosting.co.za>
In-reply-to
Content
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.  ;-)
History
Date User Action Args
2011-01-24 14:23:46sdaodensetrecipients: + sdaoden
2011-01-24 14:23:46sdaodensetmessageid: <1295879026.46.0.299345130238.issue10995@psf.upfronthosting.co.za>
2011-01-24 14:23:45sdaodenlinkissue10995 messages
2011-01-24 14:23:45sdaodencreate