[Mailman-Developers] About Mailman's unicode-enabled Message subclass

2014-12-01 Thread Aurelien Bompard
Hi * ! I'm trying to fix bug 1060951 (that I reported), and no matter how I poke at it, I can't find the proper way to solve it, so I'd like to share my thoughts with you. https://bugs.launchpad.net/mailman/+bug/1060951 The issue is with our unicode-enabled subclass of Python's email.message.Mes

[Mailman-Developers] About Mailman's unicode-enabled Message subclass

2014-12-01 Thread Stephen J. Turnbull
Aurelien Bompard writes: > I'm really interested in any insight on this issue. Thanks for reading all > that :-) RFC 2047 and RFC 2231 should be treated as wire protocol, and handled at the bytes level. I haven't looked at this in a while, but I'm pretty sure Python 3's email module does this

Re: [Mailman-Developers] About Mailman's unicode-enabled Message subclass

2014-12-01 Thread Barry Warsaw
On Dec 01, 2014, at 05:45 PM, Aurelien Bompard wrote: >I'm really interested in any insight on this issue. Thanks for reading all >that :-) To be honest, mailman.email.message.Message should really go away. It's a terrible, and old, hack. A few things *are* useful, such as pickle support (requi

Re: [Mailman-Developers] About Mailman's unicode-enabled Message subclass

2014-12-01 Thread Mark Sapiro
On 12/01/2014 08:45 AM, Aurelien Bompard wrote: > > I'm really interested in any insight on this issue. Thanks for reading all > that :-) I just took a quick look, but I think the problem is likely that mailman.email.message.Message overrides email.message.Message.__getitem__() as follows: