R. David Murray <rdmur...@bitdance.com> added the comment:
Well, "display" in the context of email includes looking at the raw email serialized as a text file. This is something one can do in most mailers. I use nmh as my mailer, which only shows raw headers, so I myself would be personally affected if headers were not normally wrapped at 78 characters when possible :) The >80 characters issue you mention is fixed by the folder used by the new API. That folder will use encoded words to wrap overlong tokens in text portions of headers, which may or may not have been the best decision (jury is still out on that one), and for non-text headers it does not put in that /n if the word won't fit on the next line if wrapped. (Or at least its not supposed to, so if you find a case where it does, please submit a bug report.) email.Header is a legacy module and no longer maintained. And yes, I realize it is used by default. There should be an open issue about going through a deprecation cycle to make the new API the default, but I've lost track and have no time to push for it myself. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35863> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
