On 2006-09-03 23:57, Jim Tittsler wrote: > I'm having a problem with subprocess .wait() on my G4 Mac running the > universal Python 2.4.3. If I do a .wait() call immediately after > creating the process object (on a very heavily loaded machine), an > "interrupted system call" exception is raised pointing at the .wait() > line. I discovered that if I insert a sleep(1) between the Popen and > wait, my command runs as expected. (The command is a rather large > mimetex[1] executable that I compiled as a universal binary.) [...] > Does anyone happen to have a clue what my larger program might be > doing that seems to trigger this race-like behavior of Popen and > wait? Or am I misusing Popen() and .wait()?
Ah. An issue in the Twisted Trac suggests that its SIGCHLD handler breaks popen(): http://twistedmatrix.com/trac/ticket/733 _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
