Message84227
| Author | jhylton |
|---|---|
| Recipients | cober, jhylton |
| Date | 2009-03-26.21:58:22 |
| SpamBayes Score | 7.310465e-05 |
| Marked as misclassified | No |
| Message-id | <1238104704.34.0.771297891758.issue5314@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I'm not sure what to do here. I guess changing to utf-8 is safe insofar as the current code only accepts ascii, so the only code that breaks will be code that depends on the encode() call raising an exception. It seems like the client out to specify the encoding, though. We could fix that via documentation. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2009-03-26 21:58:24 | jhylton | set | recipients: + jhylton, cober |
| 2009-03-26 21:58:24 | jhylton | set | messageid: <1238104704.34.0.771297891758.issue5314@psf.upfronthosting.co.za> |
| 2009-03-26 21:58:22 | jhylton | link | issue5314 messages |
| 2009-03-26 21:58:22 | jhylton | create | |