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 Jonas.Diemer
Recipients Jonas.Diemer, r.david.murray, vinay.sajip
Date 2014-07-03.14:33:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1404398018.67.0.593587206493.issue21912@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the explanation. Throughput is a valid reason.

Your workaround does of course work, but it means that the string formatting is always done, even if the message is filtered out.

Is this delayed logging behavior documented in any way (maybe I have overread it)? I am just trying to help people who may stumble upon this, as it cost me quite some time to figure out the resulting weird errors (especially in conjunction with Jython, which doesn't make debugging easier).

By the way, my workaround is a little different: I "forked" logging and am catching exceptions during the string formatting. This way, I can at least print out the affected logging calls for me to fix.
History
Date User Action Args
2014-07-03 14:33:38Jonas.Diemersetrecipients: + Jonas.Diemer, vinay.sajip, r.david.murray
2014-07-03 14:33:38Jonas.Diemersetmessageid: <1404398018.67.0.593587206493.issue21912@psf.upfronthosting.co.za>
2014-07-03 14:33:38Jonas.Diemerlinkissue21912 messages
2014-07-03 14:33:38Jonas.Diemercreate