[issue4491] email.Header.decode_header() doesn't work if encoded-word was separeted by CRLF

Changes by Terry J. Reedy : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue4491] email.Header.decode_header() doesn't work if encoded-word was separeted by CRLF

Changes by R. David Murray : -- priority: -> normal resolution: -> duplicate stage: -> committed/rejected superseder: -> decode_header does not follow RFC 2047 ___ Python tracker

[issue4491] email.Header.decode_header() doesn't work if encoded-word was separeted by CRLF

Tony Nelson added the comment: See patch in issue1079. I don't think email.header can require whitespace until it decodes parsed headers, as whitespace is not always required. -- nosy: +barry, tony_nelson versions: +Python 2.7 ___ Python tracker

[issue4491] email.Header.decode_header() doesn't work if encoded-word was separeted by CRLF

Tom Lynn added the comment: Duplicates issue1079. -- nosy: +tlynn ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue4491] email.Header.decode_header() doesn't work if encoded-word was separeted by CRLF

New submission from Atsuo Ishimoto <[EMAIL PROTECTED]>: email.Header.decode_header() doesn't work if encoded-word was separeted by CRLF. For exmaple, decode_header('=?iso-8859-1?q?hello?=\r\n world.') returns [('=?iso-8859-1?q?hello?=\r\n world.', None)], not [('hello', 'iso-8859-1'), (' world.