[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-06-11 Thread Roger Serwy
Roger Serwy added the comment: This issue is now fixed. Thank you everyone for helping! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker __

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-06-11 Thread Roundup Robot
Roundup Robot added the comment: New changeset ca8e86711403 by Roger Serwy in branch '2.7': #5492: Avoid traceback when exiting IDLE caused by a race condition. http://hg.python.org/cpython/rev/ca8e86711403 New changeset da852f5250af by Roger Serwy in branch '3.3': #5492: Avoid traceback when ex

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-06-11 Thread Roger Serwy
Roger Serwy added the comment: I noticed that the tracebacks didn't occur in 2.7 due to 872a3aca2120, but that patch was not grafted onto the 3.x branches. I'll take care of that. With #13495 fixed, the two errors mentioned in msg187323 do not occur with the _rev1 patch applied. -- _

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-05-07 Thread Rajanikanth Jammalamadaka
Changes by Rajanikanth Jammalamadaka : -- nosy: +Raj ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-05-05 Thread Roger Serwy
Roger Serwy added the comment: Terry, the SystemExit traceback from clicking cancel is expected given how Lib/site.py's Quitter first closes sys.stdin and then raises SystemExit. Closing sys.stdin causes the dialog, the raised exception just gets printed. We could change the behavior such that

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-05-04 Thread Ger Luijten
Ger Luijten added the comment: Hello Roger, Thanks for the clear explanation! Greetings, Ger 2013/4/20 Roger Serwy > > Roger Serwy added the comment: > > Good catch Terry! I've been testing using "python -m idlelib.idle" instead > of importing it from an interactive prompt. I'll need to reme

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-04-19 Thread Roger Serwy
Roger Serwy added the comment: Good catch Terry! I've been testing using "python -m idlelib.idle" instead of importing it from an interactive prompt. I'll need to remember to consider that test vector in the future. I figured out why those messages are popping up. The Tk event loop remains ru

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-04-18 Thread Terry J. Reedy
Terry J. Reedy added the comment: 3.4 fresh build, Win 7: ^z now disabled, as apparently intended. Without the patch ^d or window close button [x] quits Idle cleanly. >>> import idlelib.idle # ^D or [X] in Idle >>> With the patch, Idle disappears but console displays error messages. This is an

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-04-17 Thread Roger Serwy
Roger Serwy added the comment: Hello Ger, Sure, I can explain. IDLE is driven by the Tk event loop. Calls to .update() flushes all pending events and expired .after callbacks. When close() gets called in PyShell, it places the finalization of the close (using close2()) into the Tk event queu

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-04-17 Thread Ger Luijten
Ger Luijten added the comment: Hello Roger, To you and others that worked on this bug a big thanks for the extra deep dig into the chain of events to find this old bug and fix it. Impressive! Because I'm not familiar with the inner workings that cause this bug I was wondering if the kill comman

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-03-31 Thread Roger Serwy
Roger Serwy added the comment: I found the root cause of the original error. Entering "exit()" at the shell raises SystemExit which gets written to the shell's text widget. The call to actually write the text passes through .write() in Lib/idlelib/OutputWindow.py, which calls text.update(). T

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-03-30 Thread Terry J. Reedy
Terry J. Reedy added the comment: After reading the doc for IOBase.fileno: "Return the underlying file descriptor (an integer) of the stream if it exists. An OSError is raised if the IO object does not use a file descriptor." I decided that the bug is in the assumptions made by site.py. -

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2013-03-30 Thread Terry J. Reedy
Terry J. Reedy added the comment: I am presuming 2.7 has same problem since it has same code. The patch appears to give PyShell.close a return value it did not have before. Perhaps remove the return? I am slightly puzzled: self.pollinterval is 50 (millisecs). If reducing the wait from 100 to

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2011-12-22 Thread Roger Serwy
Roger Serwy added the comment: The attached patch fixes the problem. The close method does not need to wait for poll_subprocess rescheduling to stop. The subprocess will be killed, which would cause the socket to timeout. With closing=True, poll_subprocess will return and not reschedule. ---

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2011-12-18 Thread Roger Serwy
Roger Serwy added the comment: You can trigger this error every time if you change ".after(2*self.poll_interval, self.close2)" to ".after(1, self.close2)" in PyShell.py -- nosy: +serwy ___ Python tracker

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2011-12-17 Thread Boris FELD
Boris FELD added the comment: The problem still exists in trunk with 3.2 and 3.3. -- nosy: +Boris.FELD versions: +Python 3.2, Python 3.3 ___ Python tracker ___ __

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2010-02-10 Thread Sridhar Ratnakumar
Changes by Sridhar Ratnakumar : -- nosy: +srid ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2009-06-14 Thread Guilherme Polo
Guilherme Polo added the comment: I can get a similar error from time to time, just try it a couple of times and I believe you should hit it too. When that error isn't thrown IDLE prints the traceback of a SystemExit exception inside IDLE right before closing, so it may be hard to notice. The

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2009-04-26 Thread Daniel Diniz
Daniel Diniz added the comment: Cannot confirm on Kubuntu 8.04, Python 3.1a2+ built from source, tkinter.TkVersion is 8.5. -- nosy: +ajaksu2, gpolo priority: -> normal stage: -> test needed type: crash -> behavior ___ Python tracker

[issue5492] Error on leaving IDLE with quit() or exit() under Linux

2009-03-15 Thread Ger Luijten
New submission from Ger Luijten : Hello developers, Found a small error when using IDLE Version 3.1a1 under Kubuntu Linux 8.10 in the terminal. Kubuntu is fully updated and no installation errors for Python 3.1a1. See the listing from my installation notes below. Greetings, Ger Let's see if