[issue11216] email.message.Message set_charset does not encode properly?

R. David Murray added the comment: I've committed the patch as is. We'll address improving the semantics one way or another as part of email6 development. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___

[issue11216] email.message.Message set_charset does not encode properly?

Roundup Robot added the comment: New changeset 43ccd051ec6c by R David Murray in branch '2.7': Merge #11216: document all possible set_charset execution paths. http://hg.python.org/cpython/rev/43ccd051ec6c -- ___ Python tracker

[issue11216] email.message.Message set_charset does not encode properly?

Roundup Robot added the comment: New changeset cf1859f9aed9 by R David Murray in branch '3.1': #11216: document all possible set_charset execution paths. http://hg.python.org/cpython/rev/cf1859f9aed9 New changeset 4d25b9d2aa05 by R David Murray in branch '3.2': Merge #11216: document all possib

[issue11216] email.message.Message set_charset does not encode properly?

R. David Murray added the comment: Discussion of the new API, and what changes will be made for 3.3, will take place on the email-sig mailing list (see http://mail.python.org). Please join! Right now it is a dormant list, but I plan to post some stuff soon :) The more I stare at the set_cha

[issue11216] email.message.Message set_charset does not encode properly?

Shay Rojansky added the comment: Thanks and no problem for me, the workaround (deleting the header) works just fine. I'm not sure if/when the more general discussion on the package will take place (low-level vs. high-level), I would be interested in following. -- ___

[issue11216] email.message.Message set_charset does not encode properly?

R. David Murray added the comment: While your idea has merit, we can only add a parameter in a new version (not in a bug-fix release), so the doc fix is all we can do before 3.3. -- versions: +Python 2.7, Python 3.2, Python 3.3 -Python 2.6 ___ Pytho

[issue11216] email.message.Message set_charset does not encode properly?

Shay Rojansky added the comment: Sorry for disappearing, will be following this closer from now on. Thanks for the responses (and the acknowledgement of a problem), David and Steffen. I understand the API design philosophy and the need to allow the production of invalid messages. The main pr

[issue11216] email.message.Message set_charset does not encode properly?

Steffen Daode Nurpmeso added the comment: Shay.Rojansky: because of the fact that i needed a free last saturday for just having the time to click around a bit to find the relevant docs in the python.org jungle ... and *especially*

[issue11216] email.message.Message set_charset does not encode properly?

R. David Murray added the comment: Well, the docs don't say that the headers will be removed or modified as needed, only added as needed ;/. And in fact the set_charset code does "if 'Content-Transfer-Encoding' not in self". set_payload also says it is the caller's responsibility to "mainta

[issue11216] email.message.Message set_charset does not encode properly?

Shay Rojansky added the comment: Sorry, the "print part" below doesn't work on Python3 (I'm back in 2.6), but I see the same trouble by using part.__str__() -- ___ Python tracker _

[issue11216] email.message.Message set_charset does not encode properly?

New submission from Shay Rojansky : This may be my misunderstanding of the correct behavior, thanks in advance for your patience... The issue happens when calling set_charset (or set_payload charset) after a Message has already been created and contains a Content-Transfer-Encoding header. Her