[issue44163] IDLE ValueError in HyperParser

Terry J. Reedy added the comment: For now, I want to just improve the error message and then close. -- ___ Python tracker ___ ___

[issue44163] IDLE ValueError in HyperParser

Tal Einat added the comment: I took a look but can't see any obvious bugs there. ISTM that's a rather harmless edge case. I can't think of anything to do with this except to close for now, and reopen if this pops up again. Thinking a few steps forward, to make sense of such issues, it

[issue44163] IDLE ValueError in HyperParser

Terry J. Reedy added the comment: So, consider both possibilities where relevant. In the future, I will assume that you are running standard, up-to-date, Mac build unless you say otherwise. I presume you start IDLE from terminal and check it before shutting down. I have wondered whether

[issue44163] IDLE ValueError in HyperParser

Raymond Hettinger added the comment: I constantly move back and forth between the editor and the shell, so am not sure where the issue occurred. Also, I've never seen this one before so it isn't easily triggered. Am running Python 3.9.5 in class. Am not using a special build, it is the

[issue44163] IDLE ValueError in HyperParser

Terry J. Reedy added the comment: Thank you for the report. Which 3.9.? hyperparser has not changed in a year, but some of the calltip logic has. This occurred when you typed a '(' and IDLE tried to open a calltip but failed, and you did not notice its absence. Easy when not looking for

[issue44163] IDLE ValueError in HyperParser

New submission from Raymond Hettinger : Here's a new error that I hadn't seen before. I occurred at some point during a full day training session, so am not sure what triggered the failure: Exception in Tkinter callback Traceback (most recent call last): File