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 jonathan-lp
Recipients SilentGhost, jonathan-lp, paul.moore, steve.dower, tim.golden, vinay.sajip, zach.ware
Date 2019-06-01.19:03:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559415790.19.0.0400659188798.issue37111@roundup.psfhosted.org>
In-reply-to
Content
> I have no idea what you mean by this.

I don't see how I can be clearer. What are the reasons for NOT implementing logging to file be unicode as a default? Logging to screen is unicode as a default. What are the reasons for not wanting consistency?

> A simple Internet search for "basicConfig encoding" yields for me as the second result this Stack Overflow question 

Indeed, and it was from that question I got my solution in fact. The problem was the 30-60 minutes I wasted before that trying to figure out why my program was crashing and why it was only crashing *sometimes*. I'd written the logging part of the program a year ago and not really touched it since, so the logging module being a possible culprit was not even in my mind when the program crashed.

> As my example illustrated, it's quite easy to log Unicode in log files.

Yes, things are easy when you know it's necessary. It's the process of discovery that's an unnecessary waste of people's time. That's why I raised this and that's why I would consider this a bug in my own software. It's inconsistent, it invites problems, and it wastes peoples time.
History
Date User Action Args
2019-06-01 19:03:10jonathan-lpsetrecipients: + jonathan-lp, paul.moore, vinay.sajip, tim.golden, SilentGhost, zach.ware, steve.dower
2019-06-01 19:03:10jonathan-lpsetmessageid: <1559415790.19.0.0400659188798.issue37111@roundup.psfhosted.org>
2019-06-01 19:03:10jonathan-lplinkissue37111 messages
2019-06-01 19:03:10jonathan-lpcreate