[issue35427] logging UnicodeDecodeError from undecodable strftime output

Mark Dickinson added the comment: Agreed. Thank you! -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Py

[issue35427] logging UnicodeDecodeError from undecodable strftime output

Irit Katriel added the comment: Since this is not relevant to python 3, I think this issue can be closed. -- nosy: +iritkatriel resolution: -> out of date status: open -> pending ___ Python tracker

[issue35427] logging UnicodeDecodeError from undecodable strftime output

Change by Karthikeyan Singaravelan : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue35427] logging UnicodeDecodeError from undecodable strftime output

Mark Dickinson added the comment: Here's a bug report from someone else running into the same issue on Scrapy; looks like they worked around the issue by simply removing the timezone information from the `datefmt` (which is what we ended up doing, too): https://github.com/scrapy/scrapy/issu

[issue35427] logging UnicodeDecodeError from undecodable strftime output

New submission from Mark Dickinson : We're seeing UnicodeDecodeErrors on Windows / Python 2.7 when using logging on a Japanese customer machine. The cause turns out to be in the log record formatting, where unicode fields are combined with non-decodable bytestrings coming from strftime. More