➜

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.

classification
Title: _handleError not very informative
Type: enhancement Stage: resolved
Components: Library (Lib) Versions: Python 3.4
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: pitrou, python-dev, vinay.sajip
Priority: normal Keywords:

Created on 2012-10-30 20:00 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
log.py pitrou, 2012-10-30 20:00
Messages (2)
msg174222 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2012-10-30 20:00 
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.
msg174386 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2012-10-31 23:49 
New changeset d7b868cdd9bb by Vinay Sajip in branch 'default':
Closes #16366: Improve diagnostics from handleError(). Thanks to Antoine Pitrou for the suggestion.
http://hg.python.org/cpython/rev/d7b868cdd9bb
History
Date User Action Args
2022-04-11 14:57:37adminsetgithub: 60570
2012-10-31 23:49:46python-devsetstatus: open -> closed

nosy: + python-dev
messages: + msg174386

resolution: fixed
stage: resolved
2012-10-30 20:00:29pitroucreate