Author l0nwlf
Recipients barry, bgamari, gdamjan, l0nwlf, loewis, maxua, r.david.murray, vstinner
Date 2010-04-13.03:33:45
SpamBayes Score 0.000192232
Marked as misclassified No
Message-id <1271129627.91.0.197884678794.issue1368247@psf.upfronthosting.co.za>
In-reply-to
Content
After applying maxua's patch we do not get the unicode error but as david stated the support is not there. Here is the test.

>>> import email
>>> msg = email.MIMEText.MIMEText(u'\u043a\u0438\u0440\u0438\u043b\u0438\u0446\u0430')
>>> msg.set_charset('utf8')
>>> msg.as_string()
'MIME-Version: 1.0\nContent-Transfer-Encoding: 8bit\nContent-Type: text/plain; charset="utf8"\n\n\xd0\xba\xd0\xb8\xd1\x80\xd0\xb8\xd0\xbb\xd0\xb8\xd1\x86\xd0\xb0'

This does not seems a viable general solution to the problem.

I guess, this issue should be closed and emphasis should be now on development of 'email 6.0'. By the way I mailed Marius, the author of the blog-post http://mg.pov.lt/blog/unicode-emails-in-python , if I can borrow his example for the doc-patch.
History
Date User Action Args
2010-04-13 03:33:48l0nwlfsetrecipients: + l0nwlf, loewis, barry, vstinner, gdamjan, maxua, r.david.murray, bgamari
2010-04-13 03:33:47l0nwlfsetmessageid: <1271129627.91.0.197884678794.issue1368247@psf.upfronthosting.co.za>
2010-04-13 03:33:46l0nwlflinkissue1368247 messages
2010-04-13 03:33:45l0nwlfcreate