Message182899
| Author | r.david.murray |
|---|---|
| Recipients | BreamoreBoy, antroy, mkam, r.david.murray |
| Date | 2013-02-24.22:16:38 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1361744198.47.0.993572170811.issue1613500@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
As far as I can see from a quick look, the problem this patch addresses still exists in Python3, and in Python3 it be (more of?) a bug. That is, the output file is opened in text mode, regardless of whether the input mode was text or bytes. I'm not sure about the solution; it seems like it makes more sense to deduce the output mode from the input mode. The test changes, though, are obsolete. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2013-02-24 22:16:38 | r.david.murray | set | recipients: + r.david.murray, mkam, antroy, BreamoreBoy |
| 2013-02-24 22:16:38 | r.david.murray | set | messageid: <1361744198.47.0.993572170811.issue1613500@psf.upfronthosting.co.za> |
| 2013-02-24 22:16:38 | r.david.murray | link | issue1613500 messages |
| 2013-02-24 22:16:38 | r.david.murray | create | |