[issue14440] Close background process if IDLE closes abnormally.

Andrew Svetlov added the comment: outdated -- resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracker ___

[issue14440] Close background process if IDLE closes abnormally.

Changes by Mark Roseman : -- nosy: +markroseman ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue14440] Close background process if IDLE closes abnormally.

Changes by Terry J. Reedy : -- versions: +Python 2.7, Python 3.4 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14440] Close background process if IDLE closes abnormally.

Roger Serwy added the comment: Andrew, the reason the subprocess is not closing is due to a thread management problem. I found that a dummy thread handles cvar.wait() which is why the subprocess fails to terminate properly. If you change the tight loop in _getresponse to be: while myseq

[issue14440] Close background process if IDLE closes abnormally.

Andrew Svetlov added the comment: I still prefer to check in subprocess for parent proc existing. -- ___ Python tracker ___ ___ Pytho

[issue14440] Close background process if IDLE closes abnormally.

Roger Serwy added the comment: This bug is related to issue12540. The approach taken there is to have the IDLE frontend explicitly kill the subprocess. It's a band-aid to the problem that run.py doesn't exit when the socket to the IDLE frontend closes (either by shell restart or kill -9 on ID

[issue14440] Close background process if IDLE closes abnormally.

Andrew Svetlov added the comment: We can install signal handlers for everything what can stop process but I prefer to pass IDLE pid to subintepreter and periodically check for prime process existing. -- ___ Python tracker

[issue14440] Close background process if IDLE closes abnormally.

Terry J. Reedy added the comment: Just a bit more info: ^D and ^\ in Command Prompt interpreter print '^D' or '^\'. Return causes syntax error. ^Z\n in interpreter causes silent close. (Because DOS used ^Z as end-of-file.) ^D in IDLE causes silent close. IDLE ignores ^\ and ^Z both -- nothing

[issue14440] Close background process if IDLE closes abnormally.

Andrew Svetlov added the comment: 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 Wi

[issue14440] Close background process if IDLE closes abnormally.

Terry J. Reedy added the comment: Andrew: I strongly agree with the goal that IDLE should not leave zombie processes. The background process should die if either 1) IDLE restarts the shell with a new background process, as with every edit-run cycle, or 2) IDLE dies. The desired behavior seems

[issue14440] Close background process if IDLE closes abnormally.

Roger Serwy added the comment: I can confirm this problem with Ubuntu 11.04. -- nosy: +serwy ___ Python tracker ___ ___ Python-bugs-l

[issue14440] Close background process if IDLE closes abnormally.

Changes by Andrew Svetlov : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue14440] Close background process if IDLE closes abnormally.

Andrew Svetlov added the comment: I use Ubuntu Linux 11.10 Hmm, you are right: background process dies. But I'm pretty sure when I worked on IDLE bugs three weeks ago sometimes that process remained to live forever. Aahh. At least sending SIGTERM (kill -9) to foreground IDLE process doesn't

[issue14440] Close background process if IDLE closes abnormally.

Terry J. Reedy added the comment: You need to specify os (with version) *nix? There have been issues like this before, for earlier Python version, at least for Windows XP, which have been fixed, at least for Windows. I think last patch (a year ago? before 3.2 I think) switched to using subproc

[issue14440] Close background process if IDLE closes abnormally.

Changes by Andrew Svetlov : -- components: +IDLE ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue14440] Close background process if IDLE closes abnormally.

New submission from Andrew Svetlov : Now if IDLE was ran from console and then terminated by or kill signal — background process keep living forever. That process have to stop itself if there are no frontend IDLE. -- assignee: asvetlov messages: 157043 nosy: asvetlov priority: normal