You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/vsajip'closed_at=<Date2007-01-15.16:48:59.000>created_at=<Date2006-09-06.12:57:16.000>labels= ['type-feature', 'library']
title='Print full exceptions as they occur in logging'updated_at=<Date2007-01-15.16:48:59.000>user='https://bugs.python.org/hoffman'
Sometimes exceptions occur when using logging that are
caused by the user code. However, logging catches these
exceptions and does not give a clue as to where the
error occurred. Printing full exceptions as suggested
in RFE http://www.python.org/sf/1553375 would be a big
help.
Logging now catches very few exceptions: if logging.raiseExceptions is set to 1 (the default), exceptions are generally raised. There have been recent changes in logging to reduce the number of bare except: clauses, so I am closing this item as I believe it has been adequately addressed.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: