Feature Requests item #1553380, was opened at 2006-09-06 12:57 Message generated for change (Comment added) made by vsajip You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1553380&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Python Library Group: Python 2.6 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Michael Hoffman (hoffmanm) Assigned to: Vinay Sajip (vsajip) Summary: Print full exceptions as they occur in logging Initial Comment: 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. ---------------------------------------------------------------------- >Comment By: Vinay Sajip (vsajip) Date: 2007-01-15 16:48 Message: Logged In: YES user_id=308438 Originator: NO 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=355470&aid=1553380&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
