➜

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 pitrou
Recipients pitrou, vinay.sajip
Date 2012-10-30.20:00:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1351627229.78.0.21301171659.issue16366@psf.upfronthosting.co.za>
In-reply-to
Content 
logging's _handleError will tell you in which code line the error happened, but it's not very useful when application code has its own logging wrappers. You need more of the stack to get useful information. The attached script showcases this, along with a possible solution.
History
Date User Action Args
2012-10-30 20:00:29pitrousetrecipients: + pitrou, vinay.sajip
2012-10-30 20:00:29pitrousetmessageid: <1351627229.78.0.21301171659.issue16366@psf.upfronthosting.co.za>
2012-10-30 20:00:29pitroulinkissue16366 messages
2012-10-30 20:00:29pitroucreate