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 mdt
Recipients mdt, vinay.sajip
Date 2013-08-06.23:00:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
yes, seeing the erranous line where the wrong formatstring comes from is nice but sometimes (for myself: often) i need to know what actually was tried to be logged. this information is lost in both cases.

this is especially sad if you have long-running processes that encounter an error after a long time and that error is logged but the logging itself fails due to formatting issues. i suggest to log whatever is avaiable in the suggested way to at least see this valuable information. the additional information where it comes from for further fixing is apreaciated as well. btw: the stackstrace of the logging internals could be left out in my oppinion, it just pollutes the output with no means to the programer.
Date User Action Args
2013-08-06 23:00:49mdtsetrecipients: + mdt, vinay.sajip
2013-08-06 23:00:48mdtsetmessageid: <>
2013-08-06 23:00:48mdtlinkissue18671 messages
2013-08-06 23:00:48mdtcreate