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

miss-islington added the comment: New changeset 464c1ec65af2c1c1d849d50d9726fa453804e70e by Miss Islington (bot) in branch '3.7': bpo-15115: Document deprecation of email.encoders in Python 3 (GH-5354) https://github.com/python/cpython/commit/464c1ec65af2c1c1d849d50d9726fa453804e70e

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

Change by Cheryl Sabella : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.8 -Python 2.7, Python 3.6 ___ Python tracker ___

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

Change by miss-islington : -- pull_requests: +13596 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/13709 ___ Python tracker ___

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

Cheryl Sabella added the comment: New changeset a747c3a5edf21fa5670bc30f5e1d804de89ebf62 by Cheryl Sabella in branch 'master': bpo-15115: Document deprecation of email.encoders in Python 3 (GH-5354) https://github.com/python/cpython/commit/a747c3a5edf21fa5670bc30f5e1d804de89ebf62

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

Cheryl Sabella added the comment: Hi David, I've made a pull request for the way I think you wanted this documented. Please take a look and let me know if it's even close to what you were suggesting. Thanks! :-) -- stage: patch review -> needs patch

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

Change by Cheryl Sabella : -- keywords: +patch pull_requests: +5200 stage: needs patch -> patch review ___ Python tracker ___

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

R. David Murray added the comment: I believe so. For python3 I think it should only apply to the legacy API docs (you would use set_content (directly or indirectly) in python3, not set_payload). I've updated the versions. -- versions: +Python 3.6, Python 3.7

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

Cheryl Sabella added the comment: Barry/David, Is this still a change you wanted to include in the documentation? Thanks! -- nosy: +csabella ___ Python tracker

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

New submission from Sergei Stolyarov ser...@regolit.com: Here is the test script: -- from email.mime.text import MIMEText from email.mime.multipart import MIMEMultipart from email import encoders msg = MIMEMultipart() msg['Subject'] = 'Bug test' text_part = MIMEText('actual

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

R. David Murray rdmur...@bitdance.com added the comment: First of all, I presume you are running this in python2.7, since it doesn't work in python3. In Python3 MIMEText takes a string as input, not a bytes object, unless you pass it a _charset parameter. If you do that, the encoding is

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

R. David Murray rdmur...@bitdance.com added the comment: Barry: I think we should documentationally deprecate the encoders module. I can't see any utility in a new program calling those functions explicitly, especially if the program ever wants to port to Python3. Or maybe the Python2 docs

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

Barry A. Warsaw ba...@python.org added the comment: On Jun 20, 2012, at 01:58 PM, R. David Murray wrote: Barry: I think we should documentationally deprecate the encoders module. I can't see any utility in a new program calling those functions explicitly, especially if the program ever wants

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

Barry A. Warsaw ba...@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

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

R. David Murray rdmur...@bitdance.com added the comment: I think so, yes. When we have the mimeregistry equivalent of the headerregistry, the new mime Message classes can have a set_charset with a different implementation. I'll want to talk about the API details on email-sig before I do