[issue39071] email.parser.BytesParser - parse and parsebytes work not equivalent

Change by Abhilash Raj : -- nosy: +maxking ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue39071] email.parser.BytesParser - parse and parsebytes work not equivalent

R. David Murray added the comment: All of which isn't to discount that you might have a found a bug, by the way, if you want to investigate further :) -- ___ Python tracker _

[issue39071] email.parser.BytesParser - parse and parsebytes work not equivalent

R. David Murray added the comment: The problem is that you are starting with different inputs. unicode strings and bytes are different things, and so parsing them can produce different results. The fact of that matter is that email messages are defined to be bytes, so parsing a unicode str

[issue39071] email.parser.BytesParser - parse and parsebytes work not equivalent

Manfred Kaiser added the comment: I think, the best way is to fix the documentation. The reason is, when a developer rely to the behavior of the function but the behavior is changed, a program may work incorrect. Just think about forensic stuff. If a hash value will be created with the "par

[issue39071] email.parser.BytesParser - parse and parsebytes work not equivalent

New submission from Manfred Kaiser : I used email.parser.BytesParser for parsing mails. In one programm I used parse, because the email was stored in a file. In a second programm the email was stored in memory as a bytes object. I created hash values from each parts an compared them, to check

[issue39071] email.parser.BytesParser - parse and parsebytes work not equivalent

Change by Manfred Kaiser : Added file: https://bugs.python.org/file48786/test.py ___ Python tracker ___ ___ Python-bugs-list mailing list Un