Hi Jeremy<br><br><div><span class="gmail_quote">On 5/28/07, <b class="gmail_sendername">Jeremy Moskovich</b> <<a href="mailto:jeremy.moskovich@mobileye.com">jeremy.moskovich@mobileye.com</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
Hi,<br>I'm having consistent problems using the python subprocess module in<br>PyQT applications.<br><br>os.read() & os.wait() calls seem to be interrupted intermittently, in a<br>manner similar to the following stack trace:
<br><br>File "/homes/jeremym/programs/python2.5/lib/python2.5/subprocess.py",<br>line 593, in __init__<br>errread, errwrite)<br>File "/homes/jeremym/programs/python2.5/lib/python2.5/subprocess.py",<br>
line 1046, in _execute_child<br>data = os.read(errpipe_read, 1048576) # Exceptions limited to 1 MB<br>OSError: [Errno 4] Interrupted system call<br><br>The only mention I could find about this online is at:<br><a href="http://mail.python.org/pipermail/python-list/2007-February/427031.html">
http://mail.python.org/pipermail/python-list/2007-February/427031.html</a><br>which just recommends retrying the operation.<br></blockquote></div><br>I've never experienced an interruption during the construction of a Popen object, which seems to be the case here. Calls to
Popen.wait, on the other hand, did get interrupted all the time on OS X (no idea why), so I had to catch EINTR and retry. Are you using the very latest Python though? I have version 2.5.1 on Ubuntu, and from browsing subprocess.py
I see that os.read is now wrapped, so that the operation is always retried upon EINTR.<br><br>Hope this helps,<br>Arve<br>