On Feb 18, 10:23 am, Jean-Paul Calderone
calderone.jeanp...@gmail.com wrote:
The exception is caused by a syscall returning EINTR. A syscall will
return EINTR when a signal arrives and interrupts whatever that
syscall
was trying to do. Typically a signal won't interrupt the syscall
unless
In article
b3ebf4ec-e0bc-4bfc-8c29-368fee488...@l18g2000yqm.googlegroups.com,
Philip Winston pwins...@gmail.com wrote:
We have a multiprocess Python program that uses Queue to communicate
between processes. Recently we've seen some errors while blocked
waiting on Queue.get:
IOError:
On Feb 17, 8:46 pm, Philip Winston pwins...@gmail.com wrote:
We have a multiprocess Python program that uses Queue to communicate
between processes. Recently we've seen some errors while blocked
waiting on Queue.get:
IOError: [Errno 4] Interrupted system call
What causes the exception? Is
We have a multiprocess Python program that uses Queue to communicate
between processes. Recently we've seen some errors while blocked
waiting on Queue.get:
IOError: [Errno 4] Interrupted system call
What causes the exception? Is it necessary to catch this exception
and manually retry the Queue
On Fri, Feb 18, 2011 at 11:46 AM, Philip Winston pwins...@gmail.com wrote:
We have a multiprocess Python program that uses Queue to communicate
between processes. Recently we've seen some errors while blocked
waiting on Queue.get:
IOError: [Errno 4] Interrupted system call
What causes the
On Thu, Feb 17, 2011 at 5:46 PM, Philip Winston pwins...@gmail.com wrote:
We have a multiprocess Python program that uses Queue to communicate
between processes. Recently we've seen some errors while blocked
waiting on Queue.get:
IOError: [Errno 4] Interrupted system call
What causes the
