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.

Author asvetlov
Recipients asvetlov, roger.serwy, terry.reedy
Date 2012-03-31.20:02:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333224133.51.0.883036758783.issue14440@psf.upfronthosting.co.za>
In-reply-to
Content
Terry, sorry.

That's definitely posix-specific bug. I'll make a patch assuming Windows works well with killing IDLE.

To be polite I'll describe used signal names shortly.

SIGKILL, SIGTERM, SIGINT and SIGQUIT are used to stop process.
— SIGKILL is mimic to Windows TerminateProcess in some way. 
  It cannot be overloaded by target process and unconditionally terminates one.
— SIGTERM is default signal for kill utility. Used to stop process by some program.
— SIGINT sent if user press Ctrl+C in terminal. 
  Overridden very often.
  Python does it itself to translate this signal to KeyboardInterrupt exception.
— SIGQUIT bound to Ctrl+\ and used to stop program with memory dump. 
  The standard way to process it 
  (if need to, the most programs leaves that handler untouched) is: 
  close used resources and maybe write to stderr/logs some message. 
  Usually SIGQUIT sent to hang program to stop execution 
  if Ctrl+C doesn't help but potentially dangerous SIGKILL is not desirably 
  by risk of lacking important data or locking kernel objects.
History
Date User Action Args
2012-03-31 20:02:13asvetlovsetrecipients: + asvetlov, terry.reedy, roger.serwy
2012-03-31 20:02:13asvetlovsetmessageid: <1333224133.51.0.883036758783.issue14440@psf.upfronthosting.co.za>
2012-03-31 20:02:03asvetlovlinkissue14440 messages
2012-03-31 20:02:03asvetlovcreate