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 Piotr.Czachur, eric.araujo, vinay.sajip
Date 2011-06-15.13:59:44
SpamBayes Score 1.9609384e-05
Marked as misclassified No
Message-id <1308146385.41.0.348707147701.issue12339@psf.upfronthosting.co.za>
In-reply-to
Content
This is happening because if you pass an object instead of a string as the first argument in a logging call, it's treated as a message object whose __str__() will be called to get the actual message when it's needed, as documented here:

http://docs.python.org/howto/logging.html#arbitrary-object-messages

If, instead, you do it like this:

# coding: utf-8
import logging

logging.basicConfig()
try:
    raise Exception(u'ą')
except Exception:
    logging.getLogger('general').exception(u'An error occurred')

you get

ERROR:general:An error occurred
Traceback (most recent call last):
  File "bug_12339.py", line 6, in <module>
    raise Exception(u'ą')
Exception: \u0105
History
Date User Action Args
2011-06-15 13:59:45vinay.sajipsetrecipients: + vinay.sajip, eric.araujo, Piotr.Czachur
2011-06-15 13:59:45vinay.sajipsetmessageid: <1308146385.41.0.348707147701.issue12339@psf.upfronthosting.co.za>
2011-06-15 13:59:44vinay.sajiplinkissue12339 messages
2011-06-15 13:59:44vinay.sajipcreate