Author mkaiser
Recipients barry, mkaiser, r.david.murray
Date 2019-12-17.19:04:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1576609473.97.0.302565941716.issue39071@roundup.psfhosted.org>
In-reply-to
Content
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 "parsebytes" method and the behavior will be changed to match the behavior of the "parse" method, the the evidence can not be validated with the latest python versions.

We could add a comment to the documentation. For example "parsebytes parses the mail in a different way than parse, which may produce slightly different messages. If you rely on the same behavior for file and byte like objects you can use the parse method with BytesIO"
History
Date User Action Args
2019-12-17 19:04:33mkaisersetrecipients: + mkaiser, barry, r.david.murray
2019-12-17 19:04:33mkaisersetmessageid: <1576609473.97.0.302565941716.issue39071@roundup.psfhosted.org>
2019-12-17 19:04:33mkaiserlinkissue39071 messages
2019-12-17 19:04:33mkaisercreate