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 ale2017, barry, r.david.murray
Date 2017-02-06.14:17:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1486390679.19.0.143530578312.issue29462@psf.upfronthosting.co.za>
In-reply-to
Content
Oh, and the answer to you "why" is that the email package is only dealing with content semantically in address lists.  Everywhere else it is up to the library using program to interpret the structured headers.  In 2.7 the email package provides you the tools to process emails, but does not do very much hand holding.  The python3 email package tries to do a much better job; but, frankly, I skimped on handling comments and have done almost no testing of the code that theoretically handles them, since they are so rarely encountered in the wild.  Specifically they are supposed to be correctly parsed, but there is no way to access comment content and, as I said, there are few to zero tests that include comments to validate that syntactic handling. 

I would be interested in patches to complete the comment support in _header_value_parser in python3.
History
Date User Action Args
2017-02-06 14:17:59r.david.murraysetrecipients: + r.david.murray, barry, ale2017
2017-02-06 14:17:59r.david.murraysetmessageid: <1486390679.19.0.143530578312.issue29462@psf.upfronthosting.co.za>
2017-02-06 14:17:59r.david.murraylinkissue29462 messages
2017-02-06 14:17:58r.david.murraycreate