[issue8924] Error in error message in logging

Éric Araujo added the comment: Suggestion: To help people involved in the discussion or landing here from a Web search, you can write “fixed in rNNN” to make Roundup produce a link link this one: r81919 Thanks! -- nosy: +merwok stage: -> committed/rejected __

[issue8924] Error in error message in logging

Vinay Sajip added the comment: Fix checked into trunk and release26-maint. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue8924] Error in error message in logging

Peter Landgren added the comment: Answer to your first question: - The variable s is of type 'unicode' - The variable record.exc_text, which is what Formatter.formatException returns, is of type 'str' For your second question; I'm not a python expert, so I can't follow you there. I don't know

[issue8924] Error in error message in logging

Vinay Sajip added the comment: It seems like the logging message will be Unicode (as you have specified that it should be so) but the exception message will be string. Can you confirm whether this is the case? What type is the return value of Formatter.formatException for the specific excepti

[issue8924] Error in error message in logging

Changes by Vinay Sajip : -- assignee: -> vinay.sajip nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue8924] Error in error message in logging

New submission from Peter Landgren : This is in Windows. I got an error message in Logging in my application Gramps. However, there is an error message generated by by this logging, so the original message is never output. The last line indicate a problem with bytes in certain positions. I was a