This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients barry, bpoaugust, eric.smith, r.david.murray
Date 2022-01-18.21:03:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1642539791.9.0.261012493924.issue46392@roundup.psfhosted.org>
In-reply-to
Content
The general idea is that the string version of the header should contain all of the original information, but the parsed elements (the things returned by special header attributes) will contain the valid data, if any.  So if the string version of the header is being truncated or transformed (other than whitespace changes during re-folding), that is a bug.

Your examples involve comment fields, and I'm afraid that my development of the parser stopped before I did very much with comments.  Therefore I am not surprised that comments are handled incorrectly :( :(  They aren't very common in the wild, as far as I was able to tell. which is why they were my last priority.
History
Date User Action Args
2022-01-18 21:03:11r.david.murraysetrecipients: + r.david.murray, barry, eric.smith, bpoaugust
2022-01-18 21:03:11r.david.murraysetmessageid: <1642539791.9.0.261012493924.issue46392@roundup.psfhosted.org>
2022-01-18 21:03:11r.david.murraylinkissue46392 messages
2022-01-18 21:03:11r.david.murraycreate