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 aroberge, terry.reedy
Date 2021-06-22.17:31:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1624383102.06.0.671490953559.issue43476@roundup.psfhosted.org>
In-reply-to
Content
I can confirm that, if the existing line

type, value, tb = sys.exc_info()

in pyshell.ModifiedInterpreter.showsyntaxerror is replaced by

e_type, value, tb = sys.exc_info()
err = str((type(e_type).__name__, *value)+'\n'
linecache.cache["<SyntaxError>"] = (len(err), 0, [err], "<SyntaxError>")

then all the required information to analyze the cause of the error can be retrieved using rpc.

====
Aside: In doing various tests, I noticed that "IndentationError" are simply reported as "SyntaxError" in Idle, since at least Python 3.6.
This is just a cosmetic issue.
History
Date User Action Args
2021-06-22 17:31:42arobergesetrecipients: + aroberge, terry.reedy
2021-06-22 17:31:42arobergesetmessageid: <1624383102.06.0.671490953559.issue43476@roundup.psfhosted.org>
2021-06-22 17:31:42arobergelinkissue43476 messages
2021-06-22 17:31:41arobergecreate