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 terry.reedy
Recipients Dennis Sweeney, pablogsal, shreyanavigyan, terry.reedy
Date 2021-05-04.18:09:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1620151751.27.0.490428278232.issue44026@roundup.psfhosted.org>
In-reply-to
Content
I realized after posting that looking for close matching is a performance issue and does not need to be done unless the exception is going to be displayed.  But it is a shame to keep such great work away from many users.

What would you think of either

1. add sys.tracebackhook, to be called by the traceback display functions if not None.  Then idlelib.run.print_exception would not have to duplicate the sometimes changing logic for chaining or otherwise joining multiple tracebacks into one mega-traceback.  Instead, from what Dennis said above, it could set the hook and call the built-in exceptionhook.

2. add a new optional parameter to exceptionhook and the traceback display function.  This would have the same advantage as above.
History
Date User Action Args
2021-05-04 18:09:11terry.reedysetrecipients: + terry.reedy, pablogsal, Dennis Sweeney, shreyanavigyan
2021-05-04 18:09:11terry.reedysetmessageid: <1620151751.27.0.490428278232.issue44026@roundup.psfhosted.org>
2021-05-04 18:09:11terry.reedylinkissue44026 messages
2021-05-04 18:09:11terry.reedycreate