[docs] [issue15115] Duplicated Content-Transfer-Encoding header when applying email.encoders

[Barry A. Warsaw]

Barry A. Warsaw <barry at python.org> added the comment:

On Jun 20, 2012, at 01:51 PM, R. David Murray wrote:

>Note that I don't *like* that the current API is that calling set_charset
>does the body encode if and only if there are no existing headers, but that
>is the way it has always worked, and there are programs out there that depend
>on it.

Can we nuke that for email6?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15115>
_______________________________________