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 r.david.murray
Recipients r.david.murray, the.mulhern, vinay.sajip, yselivanov
Date 2014-03-13.21:16:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1394745386.69.0.21934908441.issue20918@psf.upfronthosting.co.za>
In-reply-to
Content
Logging tries to catch errors during logging and log them.  This is an edge case it doesn't handle, because when it tries to log it...it tries to print the arguments, and of course the repr of the argument fails (again).

So I think this is a bug.
History
Date User Action Args
2014-03-13 21:16:26r.david.murraysetrecipients: + r.david.murray, vinay.sajip, yselivanov, the.mulhern
2014-03-13 21:16:26r.david.murraysetmessageid: <1394745386.69.0.21934908441.issue20918@psf.upfronthosting.co.za>
2014-03-13 21:16:26r.david.murraylinkissue20918 messages
2014-03-13 21:16:26r.david.murraycreate