[issue29993] error of parsing encoded words in email of standard library

R. David Murray added the comment: Actually, looking at the issue related to the patch, we conferred at the time, Barry, and decided on no backports. It was applied only to default. Sijian: the reason we put the issue number in the commit message is because the issue often contains relevant

[issue29993] error of parsing encoded words in email of standard library

R. David Murray added the comment: I consciously decided not to backport this to 2.7 at the time, though I'm not sure I said that out loud. I think it is too much of a behavior change for 2.7. -- resolution: -> rejected stage: -> resolved status: open -> closed

[issue29993] error of parsing encoded words in email of standard library

Barry A. Warsaw added the comment: On Apr 05, 2017, at 03:26 PM, Raymond Hettinger wrote: >Barry, is this something that should go back to 2.7 or is that pretty much >settled business at this point? I think we should not backport this. It's a behavior change and my concern would be that

[issue29993] error of parsing encoded words in email of standard library

Raymond Hettinger added the comment: Barry, is this something that should go back to 2.7 or is that pretty much settled business at this point? -- nosy: +rhettinger ___ Python tracker

[issue29993] error of parsing encoded words in email of standard library

New submission from sijian liang: This issue is fixed in python3 see https://github.com/python/cpython/commit/07ea53cb218812404cdbde820647ce6e4b2d0f8e -- components: email messages: 291171 nosy: barry, r.david.murray, sijian liang priority: normal severity: normal status: open title: