[issue27024] IDLE shutdown glitch when started by import

Mark Roseman added the comment: tried this patch on 3.6 as per terry's previous msg; still getting same error in idle test suite on os x -- nosy: +markroseman ___ Python tracker

[issue27024] IDLE shutdown glitch when started by import

Terry J. Reedy added the comment: I applied to 2.7 after changing the file name. I still get F:\Python\dev\27>pcbuild\python_d.exe -m test.regrtest -ugui test_idle [1/1] test_idle can't invoke "event" command: application has been destroyed while executing "event generate $w <>"

[issue27024] IDLE shutdown glitch when started by import

Terry J. Reedy added the comment: This is a partial fix. Run python, import idlelib.idle, open idlelib.run, close editor, close shell, get clean >>> prompt in python. No 'bgerror ...'. This is probably enough to justify patch. (Directly opening and closing IDLE continues to work fine, as

[issue27024] IDLE shutdown glitch when started by import

Serhiy Storchaka added the comment: Proposed patch fixes the issue for all Tkinter applications. -- components: +Tkinter -IDLE keywords: +patch stage: test needed -> patch review type: -> behavior versions: +Python 2.7 Added file:

[issue27024] IDLE shutdown glitch when started by import

Serhiy Storchaka added the comment: There are few possible workarounds: 1. Catch and ignore TclError in CodeContext.timer_event, CodeContext.font_timer_event and other callbacks. 2. Save results of after() and after_idle() calls and pass them to after_cancel() before destroying widgets.

[issue27024] IDLE shutdown glitch when started by import

New submission from Terry J. Reedy: Win10, 3.5.1: Run 'python' in interactive mode. >>> import idlelib.idle # open idle shell # or import idlelib.__main__ # only works once in an interactive session as re-import does not rerun # In IDLE, open editor to some file. For instance, alt-M,