(original) (raw)
Ah, sometimes, the exception raised is following (slightly different from previous):
Exception in Tkinter callback
Traceback (most recent call last):
File "/opt/python301/lib/python3.0/tkinter/__init__.py", line 1399, in __call__
return self.func(*args)
File "/opt/python301/lib/python3.0/tkinter/__init__.py", line 487, in callit
func(*args)
File "/opt/python301/lib/python3.0/idlelib/PyShell.py", line 490, in poll_subprocess
response = clt.pollresponse(self.active_seq, wait=0.05)
File "/opt/python301/lib/python3.0/idlelib/rpc.py", line 424, in pollresponse
message = self.pollmessage(wait)
File "/opt/python301/lib/python3.0/idlelib/rpc.py", line 376, in pollmessage
packet = self.pollpacket(wait)
File "/opt/python301/lib/python3.0/idlelib/rpc.py", line 347, in pollpacket
r, w, x = select.select([self.sock.fileno()], [], [], wait)
select.error: (4, 'Interrupted system call')
In this case the IDLE not respond, because the python interpreter is not restarted. I must to close all :-(.
I will open a issue in the tracker relative to IDLE for now?
Regards.
2009/4/15 Ivan Krstić <krstic@solarsail.hcs.harvard.edu>
On Apr 15, 2009, at 10:05 AM, Alessio Giovanni Baroni wrote:See here for an explanation of the same problem in another module:
r, w, x = select.select(\[self.sock.fileno()\], \[\], \[\], wait)
select.error: (4, 'Interrupted system call')
<http://mail.python.org/pipermail/python-dev/2000-October/009671.html>
Sounds like you ought to file a bug against IDLE to have it grow EINTR handling. Cheers,
\--
Ivan Krstić <krstic@solarsail.hcs.harvard.edu> | http://radian.org