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 mdt, vinay.sajip
Date 2013-08-07.00:01:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375833696.81.0.20864048556.issue18671@psf.upfronthosting.co.za>
In-reply-to
Content
The location of the error isn't lost - that's the important thing. If it's that important that you never lose the parameters of a logging call, then you could just double check the formatting for errors, or use a specialised message object, as described in the documentation, which allows you control over the formatting:

http://docs.python.org/2/howto/logging.html#using-arbitrary-objects-as-messages
History
Date User Action Args
2013-08-07 00:01:36vinay.sajipsetrecipients: + vinay.sajip, mdt
2013-08-07 00:01:36vinay.sajipsetmessageid: <1375833696.81.0.20864048556.issue18671@psf.upfronthosting.co.za>
2013-08-07 00:01:36vinay.sajiplinkissue18671 messages
2013-08-07 00:01:36vinay.sajipcreate