Message106837
Ah, it's not 100% true that it doesn't change "working" behavior. Before the patch, the first example in this ticket doesn't raise an error until the as_string call. After this patch, the error is raised as soon as MIMEText is called without the charset parameter. Since without the patch the code still fails eventually, I think this is an acceptable behavior change for a bug fix, but it does make me a little nervous :)
Updated patch with doc change to Message.set_charset attached. |
|
Date |
User |
Action |
Args |
2010-06-01 14:05:44 | r.david.murray | set | recipients:
+ r.david.murray, loewis, barry, orsenthil, vstinner, gdamjan, maxua, bgamari, l0nwlf |
2010-06-01 14:05:44 | r.david.murray | set | messageid: <1275401144.35.0.957561085878.issue1368247@psf.upfronthosting.co.za> |
2010-06-01 14:05:43 | r.david.murray | link | issue1368247 messages |
2010-06-01 14:05:42 | r.david.murray | create | |
|