[issue44660] email.feedparser: support RFC 6532 section 3.5

Francis Johnson added the comment: Hello, I haven't had the time to complete @r.david.murrary's recommendation and unfortunately don't anticipate that I will for now. Any objection to me resubmitting the pull request as-is? Alone, it still delivers business value so to speak. Thanks

[issue44660] email.feedparser: support RFC 6532 section 3.5

Francis Johnson added the comment: As requested, I’ve started testing and writing changes for the generator and content manager. I’m assuming there is no rush since the scope is now widened. Will have some follow-on questions about the design. --

[issue44660] email.feedparser: support RFC 6532 section 3.5

R. David Murray added the comment: Having looked at the cited part of the RFC (but not tried to analyze it in detail), I think you are correct. I've also glanced at your PR, and I think your approach is correct in broad outline, but I haven't looked at the details. For full message/global

[issue44660] email.feedparser: support RFC 6532 section 3.5

Francis Johnson added the comment: The first paragraph of section 3.5 states two positions that the RFC holds on Content-Transfer-Encodings: (1) “allows newly defined MIME types to permit content-transfer-encoding;” and (2) “allows content-transfer-encoding for message/global (see Section 3.7)

[issue44660] email.feedparser: support RFC 6532 section 3.5

blackrose 1337 added the comment: #44713: subprocess.rst typo ``"shell=True"`` => ``shell=True`` -- nosy: +virusdetected1337 ___ Python tracker ___

[issue44660] email.feedparser: support RFC 6532 section 3.5

Francis Johnson added the comment: Try parsing an example such as this through the Python email library: Content-Type: message/global Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; = charset=3D”us-ascii” Hello, World! You will find that the valid quoted-printable

[issue44660] email.feedparser: support RFC 6532 section 3.5

Terry J. Reedy added the comment: dont obviously *match* -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue44660] email.feedparser: support RFC 6532 section 3.5

Terry J. Reedy added the comment: RFC 6532 Internationalized Email Headers https://datatracker.ietf.org/doc/html/rfc6532 3.5. Changes to MIME Message Type Encoding Restrictions https://datatracker.ietf.org/doc/html/rfc6532#section-3.5 don't obviously "message/global Emails with non-identity