homepage

➜

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.

Recipients
Author	kbk
Date	2007年02月05日.17:40:49
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
I don't see how to easily eliminate the dialog. When quit() runs, Quitter.__call__() closes IDLE's sys.stdin, and (since __call__() is still executing) that's trapped by PyShell.py using the logic which requires the user to confirm exit if he clicks on the Shell's close widget (WM_DELETE_WINDOW) while his code is running. If File.close() had a parameter, we might be able to do something about this. The extra confirmation probably doesn't hurt. Aficionados will use Ctrl-D etc. anyway.

Content

I don't see how to easily eliminate the dialog. When quit() runs, Quitter.__call__() closes IDLE's sys.stdin, and (since __call__() is still executing) that's trapped by PyShell.py using the logic which requires the user to confirm exit if he clicks on the Shell's close widget (WM_DELETE_WINDOW) while his code is running. If File.close() had a parameter, we might be able to do something about this.
The extra confirmation probably doesn't hurt. Aficionados will use Ctrl-D etc. anyway.

History
Date	User	Action	Args
2007年08月23日 14:39:46	admin	link	issue1479785 messages
2007年08月23日 14:39:46	admin	create