Author r.david.murray
Recipients barry, bgamari, gdamjan, haypo, l0nwlf, loewis, maxua, orsenthil, r.david.murray
Date 2010-06-01.13:48:44
SpamBayes Score 0.000176921
Marked as misclassified No
Message-id <1275400128.55.0.603112232396.issue1368247@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think either of the previous patches are correct.  I found a note in Issue1685453 that Barry would like for this to work, and after poking around in the code for a bit I think it can be done without breaking anything.

Attached is a patch that adds unicode support to MIMEText, including unit tests and docs updates.  Note that it is necessary to specify a charset if you have non-ASCII text in your unicode string, since the default charset is us-ascii.  The unit tests confirm this behavior.

Now the question is, is this a bug-fix or an enhancement?  I *think* it is safe to apply and backport, since I think the only behavior it changes is to make unicode input work, whereas before it would give a traceback.  But I've been wrong before :(
History
Date User Action Args
2010-06-01 13:48:49r.david.murraysetrecipients: + r.david.murray, loewis, barry, orsenthil, haypo, gdamjan, maxua, bgamari, l0nwlf
2010-06-01 13:48:48r.david.murraysetmessageid: <1275400128.55.0.603112232396.issue1368247@psf.upfronthosting.co.za>
2010-06-01 13:48:46r.david.murraylinkissue1368247 messages
2010-06-01 13:48:45r.david.murraycreate