This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients SilentGhost, jonathan-lp, paul.moore, steve.dower, tim.golden, vinay.sajip, zach.ware
Date 2019-05-31.15:37:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559317040.27.0.794708667703.issue37111@roundup.psfhosted.org>
In-reply-to
Content
> Given that the file created by the logger is utf-8, it's unclear why it doesn't work ... I found a workaround by using a Handler

Loggers don't create files - handlers do. The file that you attached seems to be just a text file containing ASCII text. Any ASCII is also utf-8, so Notepad++'s assertion doesn't mean anything in this situation.

> so that people don't get unpleasant surprises that even more painful to debug when things only break in certain logging modes?

People have been using logging, on Windows, without problems, for years, often using utf-8 to encode their log files. Perhaps you need to read the documentation and look at examples more carefully - I'm not intending to be rude, but say that because using a handler isn't some kind of workaround, and you thinking that it was indicates that you're not sufficiently familiar with the documentation.

I'd suggest posting questions on Stack Overflow or the python-list mailing list, to establish whether there really seems to be a Python bug, before actually logging a Python issue. I appreciate that you're trying to improve Python.
History
Date User Action Args
2019-05-31 15:37:20vinay.sajipsetrecipients: + vinay.sajip, paul.moore, tim.golden, SilentGhost, zach.ware, steve.dower, jonathan-lp
2019-05-31 15:37:20vinay.sajipsetmessageid: <1559317040.27.0.794708667703.issue37111@roundup.psfhosted.org>
2019-05-31 15:37:20vinay.sajiplinkissue37111 messages
2019-05-31 15:37:20vinay.sajipcreate