[issue36261] email examples should not gratuitously mess with preamble

miss-islington added the comment: New changeset 262779fb5038db7574180c6a89b4f0968f29bd79 by Miss Islington (bot) in branch '3.8': bpo-36261: Improve example of the preamble field in email docs (GH-14751) https://github.com/python/cpython/commit/262779fb5038db7574180c6a89b4f0968f29bd79

[issue36261] email examples should not gratuitously mess with preamble

miss-islington added the comment: New changeset fb58024688050385ed2fd93caf02a5807d1ccfed by Miss Islington (bot) in branch '3.7': bpo-36261: Improve example of the preamble field in email docs (GH-14751) https://github.com/python/cpython/commit/fb58024688050385ed2fd93caf02a5807d1ccfed

[issue36261] email examples should not gratuitously mess with preamble

Steve Dower added the comment: Merged, and I am assuming the backports will merge fine too. Thanks for the patch! -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue36261] email examples should not gratuitously mess with preamble

Steve Dower added the comment: New changeset 8efade91b12a13102a09a3856179021e579da5e9 by Steve Dower (Carl Bordum Hansen) in branch 'master': bpo-36261: Improve example of the preamble field in email docs (GH-14751)

[issue36261] email examples should not gratuitously mess with preamble

Change by miss-islington : -- pull_requests: +14555 pull_request: https://github.com/python/cpython/pull/14760 ___ Python tracker ___

[issue36261] email examples should not gratuitously mess with preamble

Change by miss-islington : -- pull_requests: +14556 pull_request: https://github.com/python/cpython/pull/14761 ___ Python tracker ___

[issue36261] email examples should not gratuitously mess with preamble

Change by Steve Dower : -- versions: +Python 3.8, Python 3.9 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36261] email examples should not gratuitously mess with preamble

Carl Bordum Hansen added the comment: I also only found the one case. Submitted a patch. -- nosy: +carlbordum ___ Python tracker ___

[issue36261] email examples should not gratuitously mess with preamble

Change by Carl Bordum Hansen : -- keywords: +patch pull_requests: +14546 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/14751 ___ Python tracker

[issue36261] email examples should not gratuitously mess with preamble

Change by R. David Murray : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36261] email examples should not gratuitously mess with preamble

R. David Murray added the comment: We could also change both of them to be more correct and say something like "If you are reading this your browser probably does not support MIME, and you will have to find a MIME aware email client or decode the message by hand." That demonstrates what

[issue36261] email examples should not gratuitously mess with preamble

R. David Murray added the comment: I don't see "several", can you point to the other instances? I only see that one case you mention (for reference, it is in Doc/includes/email-mime.py). The other case of setting preamble is actually correct ("You will not see this in a MIME-aware mail

[issue36261] email examples should not gratuitously mess with preamble

New submission from era : Several of the examples in the email module documentation modify the preamble. This is not good practice. The email MIME preamble is really only useful for communicating information about MIME itself, not for general human-readable content like 'Our family reunion'.