Yonas <yona...@gmail.com> added the comment: http://groups.google.com/group/comp.lang.python/browse_thread/thread/9a853d0308c8e55a
"I'm also glad to see a test case that causes exactly the same error with or without the presence of a ‘daemon.DaemonContext’. Further research shows that handling of ‘SIGCLD’ (or ‘SIGCLD’) is fairly OS-specific, with “ignore it” or “handle it specifically” being correct on different systems. I think Python's default handling of this signal is already good (modulo bug #1731717 to be addressed in ‘subprocess’). So I will apply a change similar to Joel Martin's suggestion, to default to avoid touching the ‘SIGCLD’ signal at all, and with extra notes in the documentation that anyone using child processes needs to be wary of signal handling. This causes the above test case to succeed; the output file contains:: ===== Child process via os.system. Child process via 'subprocess.Popen'. Parent daemon process. Parent daemon process done. =====" -- By Ben Finney ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1731717> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
