subject:"\[issue1681333\] email.header unicode fix"

[issue1681333] email.header unicode fix

2011-03-17 Thread Barry A. Warsaw

Barry A. Warsaw added the comment: Sadly, I agree with RDM. There are too many workarounds in the field for this bug so it can really only be fixed in email6. -- ___ Python tracker

[issue1681333] email.header unicode fix

2011-03-17 Thread R. David Murray

R. David Murray added the comment: Yes, I can well understand that feeling. I've only relatively recently taken over maintaining the email package. I'm working my way through the old bug queue, and I can only deal with them in the context in which I find them. -- ___

[issue1681333] email.header unicode fix

2011-03-16 Thread Tokio Kikuchi

Tokio Kikuchi added the comment: OK. I understand but slightly disappointed because four years have passed since this issue was raised and these years are included in the 'such long standing' period. -- ___ Python tracker

[issue1681333] email.header unicode fix

2011-03-16 Thread R. David Murray

R. David Murray added the comment: I'm rejecting this. There is more than one bug here, but it starts with the fact that ('xxx', None) is treated the same as ('xxx', 'us-ascii'). In the first case it would be nice if a space was used to separate two of them in a row. In the second case a s

[issue1681333] email.header unicode fix

2011-03-13 Thread R. David Murray

Changes by R. David Murray : -- versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3 -Python 2.6 ___ Python tracker ___ ___ Pyt

[issue1681333] email.header unicode fix

2010-07-17 Thread Mark Lawrence

Mark Lawrence added the comment: Applied the patches to the test files for 2.6.5 without patching header.py and got one failure. FAIL: test_i18nheader_unicode (email.test.test_email.TestRFC2047) I also expected a failure from the equivalent test for test_email_renamed, can someone please adv