[issue21973] Idle should not quit on corrupted user config files

Changes by Mark Roseman : -- nosy: +markroseman ___ Python tracker ___ ___

[issue21973] Idle should not quit on corrupted user config files

Terry J. Reedy added the comment: config-xyz.bad? I have not look at the tests, but they should be relevant, just in need of changing to using mock message boxes from idle_test/mock_tk.py. -- ___ Python tracker rep...@bugs.python.org

[issue21973] Idle should not quit on corrupted user config files

ingrid added the comment: Here is a patch that will print a warning if there is an invalid config when starting idle. Example: Warning (from warnings module): File /Users/ingrid/.idlerc/config-extensions.cfg, line 1 enable=1 MissingSectionHeaderError: File contains no section headers.

[issue21973] Idle should not quit on corrupted user config files

Terry J. Reedy added the comment: Some background context before I comment on the patch: Printing warnings to a console is a flawed idea. It does not work on Windows when Idle is run with pythonw and there is no console to write to. This is the normal case on Windows and, I suspect, the

[issue21973] Idle should not quit on corrupted user config files

ingrid added the comment: Thanks for your feedback. I can try again when you have written the config warn function or I can try writing the config warn function. The tests aren't relevant anymore if the warning is raised in a tk message box. I think deleting the config files could potentially

[issue21973] Idle should not quit on corrupted user config files

Terry J. Reedy added the comment: Explanation: there are a few config-xy files in lib/idlelib that contain default configuration values. Custom values for a particular user, which override the defaults, are kept in a .idlerc directory placed in a users home directory (here C:/users/Tomk).