This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Sharebear
Recipients Sharebear, barry, loewis
Date 2008-01-19.10:02:40
SpamBayes Score 0.0070552775
Marked as misclassified No
Message-id <>

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 any way other than reading 
the source or writing a test case (and that would require understanding 
what the email.mime module was doing "under the hood") for a developer 
to find out which Content-Transfer-Encoding was going to be used.

Also, just from a usability point of view I would expect that creating 
an invalid mime part would be a little more difficult. Especially 
considering the fix should be as small as adding "if not encoding in 
valid encodings: raise SensibleException".
Date User Action Args
2008-01-19 10:02:42Sharebearsetspambayes_score: 0.00705528 -> 0.0070552775
recipients: + Sharebear, loewis, barry
2008-01-19 10:02:41Sharebearsetspambayes_score: 0.00705528 -> 0.00705528
messageid: <>
2008-01-19 10:02:41Sharebearlinkissue1823 messages
2008-01-19 10:02:40Sharebearcreate