Message164623
| Author | v+python |
|---|---|
| Recipients | Ben.thelen, ezio.melotti, ned.deily, terry.reedy, v+python |
| Date | 2012-07-03.20:52:22 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1341348742.93.0.0632877268009.issue12967@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
So this looks like it might be a simple fix... in issue 1602, there was a patch for Windows console for 3.1... sadly not applied then, or 3.2, or 3.3 (yet). But in 3.2, the fix sprouted a failure just like this one: the console output class would get reported to not have an "errors" attribute when doing an input. A fix there was to add an attribute errors='strict' to the console output class. Here it seems the same symptom sprouted in the same time frame, for a similar situation where the output class has been replaced by one that doesn't have an errors attribute... so it should grow one... |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-07-03 20:52:23 | v+python | set | recipients: + v+python, terry.reedy, ned.deily, ezio.melotti, Ben.thelen |
| 2012-07-03 20:52:22 | v+python | set | messageid: <1341348742.93.0.0632877268009.issue12967@psf.upfronthosting.co.za> |
| 2012-07-03 20:52:22 | v+python | link | issue12967 messages |
| 2012-07-03 20:52:22 | v+python | create | |