Message133028
| Author |
r.david.murray |
| Recipients |
ajaksu2, barry, iko, r.david.murray |
| Date |
2011年04月05日.13:18:17 |
| SpamBayes Score |
3.6048255e-06 |
| Marked as misclassified |
No |
| Message-id |
<1302009499.01.0.629680538831.issue975330@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Well, it's two years later, but I did look at this during the sprints at PyCon, though I didn't get as far as posting it then (I only just now rediscovered the patch on my laptop).
Python3 no longer has a "binary" flag on base64mime.encode, so here is a proposed patch for Python3. I'm not sure if this should be backported or not, but I'm leaning that way. Theoretically it should be only an improvement, but I can easily imagine unix-only programs unknowingly depending on the previous non-translation of newlines. Still, since email is about intermachine communication and this clearly makes it more RFC compliant, the change is a legitimate bug fix and the chance of breakage is relatively small.
Tests are still needed. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2011年04月05日 13:18:19 | r.david.murray | set | recipients:
+ r.david.murray, barry, iko, ajaksu2 |
| 2011年04月05日 13:18:19 | r.david.murray | set | messageid: <1302009499.01.0.629680538831.issue975330@psf.upfronthosting.co.za> |
| 2011年04月05日 13:18:18 | r.david.murray | link | issue975330 messages |
| 2011年04月05日 13:18:17 | r.david.murray | create |
|