Martin Panter added the comment: I think Karl’s original report was mainly about normal signal handling in the long term in the child, i.e. behaviour after exec() succeeds.
Ian, your problem sounds more like a bug or unfortunate quirk of the window between fork() and exec(). Maybe it is possible to solve it by blocking or resetting signal handlers, or using posix_spawn() (Issue 20104). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25787> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
