Message344059
| Author | SilentGhost |
|---|---|
| Recipients | SilentGhost, jonathan-lp, vinay.sajip |
| Date | 2019-05-31.10:27:59 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1559298479.09.0.14520712893.issue37111@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> Given that the file created by the logger is utf-8 I don't think this is true. Default file handler created using filename argument is opened with encoding None (meaning that it relies on system-default encoding, which is on Windows is not utf-8). And it also explains why your work-around works, provided you've opened file handler with explicit utf-8 encoding. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-05-31 10:27:59 | SilentGhost | set | recipients: + SilentGhost, vinay.sajip, jonathan-lp |
| 2019-05-31 10:27:59 | SilentGhost | set | messageid: <1559298479.09.0.14520712893.issue37111@roundup.psfhosted.org> |
| 2019-05-31 10:27:59 | SilentGhost | link | issue37111 messages |
| 2019-05-31 10:27:59 | SilentGhost | create | |