[issue1823] Possible to set invalid Content-Transfer-Encoding on email.mime.multipart.MIMEMultipart

Jonathan Share added the comment: Martin, I can almost agree with you _if_ I was setting the Content-Transfer- Encoding myself, however I am not. I am setting the charset and the library chooses an appropriate Content-Transfer-Encoding to represent the mime part with. Currently I can't see

[issue1822] email.mime.multipart.MIMEMultipart.is_multipart() returns false before items have been added.

Jonathan Share added the comment: Attaching a patch for the quick fix I proposed below. I would still like to see some feedback regarding making the design of the mime module more object oriented. email.Message really shouldn't be making assumtions about how subclasses represent their state

[issue1822] email.mime.multipart.MIMEMultipart.is_multipart() returns false before items have been added.

Changes by Jonathan Share: -- nosy: +facundobatista __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1822 __ ___ Python-bugs-list mailing list Unsubscribe: http

[issue1823] Possible to set invalid Content-Transfer-Encoding on email.mime.multipart.MIMEMultipart

Jonathan Share added the comment: I'm beginning to realise this is slightly bigger than I first thought ;-) Trying to make a nice test case for this issue, I thought it would be a good idea for the parser to register a defect for invalid content- transfer-encoding so I can test against

[issue1823] Possible to set invalid Content-Transfer-Encoding on email.mime.multipart.MIMEMultipart

Jonathan Share added the comment: Run out of time to look at this today. In order to write a nice test case for this issue I need the parser to notice this error in messages. I've filed issue1874 for the parser not reporting the invalid cte in the msg.defects

[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages

New submission from Jonathan Share: Although the documentation of FeedParser states that It will populate a message object's defects attribute with a list of any problems it found in a message. no defect is found in the test case I am about to upload. The message in the test case is broken

[issue1874] email parser does not register a defect for invalid Content-Transfer-Encoding on multipart messages

Changes by Jonathan Share: Added file: http://bugs.python.org/file9227/issue1874.patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1874 __ ___ Python-bugs-list mailing list

[issue1822] email.mime.multipart.MIMEMultipart.is_multipart() returns false before items have been added.

New submission from Jonathan Share: Steps to reproduce == from email.mime.multipart import MIMEMultipart foo = MIMEMultipart() foo.is_multipart() False Expected Result === True should be returned from MIMEMultipart.is_multipart() Notes = Looking

[issue1823] Possible to set invalid Content-Transfer-Encoding on email.mime.multipart.MIMEMultipart

New submission from Jonathan Share: Steps to Reproduce == from email.mime.multipart import MIMEMultipart from email.mime.text import MIMEText multipart = MIMEMultipart() multipart.set_charset('UTF-8') text = MIMEText(sample text) multipart.attach(text) print