On 05/22/2013 09:46 PM, Jim Mooney wrote:
What do you mean "doesn't do anything" ? It certainly terminates the loop,
which was the intent. Provided of course that something else isn't trapping
the Ctrl-C first.
It doesn't in Windows proper, using Wing 101.
Then Wing is changing the behavior, trapping the Ctrl-C. Not sure why
you would call Wing the "proper Windows".
It does exit in the
Windows command console.
Of course.
For some reason I forgot ctrl-C is Copy in
windows.
Only to programs that have a GUI event loop which happens to trap the
event. That's common in Windows, and is required by the CUA standard
(apparently defunct), but it's not the default behavior of a Windows
executable.
I tried Ctrl-X but I was again confusing the old DOS abort
with Windows Cut. I've been enslaved by the GUI ;')
I'm using Wing 101, which doesn't have a feature set for altering that
behavior. It's probably in the professional version. If I scrape up
spare cash I may go for PyCharm or Wing Pro, but I don't need them on
the low end of the learning curve. I'd just waste time fooling with
them.
The program does exit in Idle, although Idle throws up a Tk screen
asking if you want to abort the program, so it's not a clean exit.
Jim
--
DaveA
_______________________________________________
Tutor maillist - Tutor@python.org
To unsubscribe or change subscription options:
http://mail.python.org/mailman/listinfo/tutor
