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 aroberge
Recipients AbyxDev, aroberge, miss-islington, terry.reedy
Date 2021-02-04.02:40:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1612406440.97.0.698864219334.issue43008@roundup.psfhosted.org>
In-reply-to
Content
Terry: as per your earlier comment, I have tried to use Friendly-traceback with the latest version. While it does set the exception hook correctly, it is not useful. 

Friendly-traceback (FT) needs to have access to the code that was executed. FT's REPL caches the code (similarly to what IPython does, but not CPython) prior to execution so that it can retrieve it correctly, have access to the relevant execution frame, etc.  This is not possible when using IDLE's REPL. In fact, for some types of exceptions, when FT tries to get access to the code, it ends up triggering secondary exceptions.

However, using the method describe in FT's documentation (with relies on FT's own console) still works correctly.
History
Date User Action Args
2021-02-04 02:40:41arobergesetrecipients: + aroberge, terry.reedy, miss-islington, AbyxDev
2021-02-04 02:40:40arobergesetmessageid: <1612406440.97.0.698864219334.issue43008@roundup.psfhosted.org>
2021-02-04 02:40:40arobergelinkissue43008 messages
2021-02-04 02:40:40arobergecreate