[issue20167] Exception on IDLE closing

Terry J. Reedy added the comment: Serhiy, I responded to your report and followups on a new issue, #22614. Tal, if you can, please test ./python -m idlelib.idle Lib/decimal.py on OSX and respond there. -- resolution: -> fixed stage: test needed -> resolved status: open -> closed _

[issue20167] Exception on IDLE closing

Serhiy Storchaka added the comment: Changing update() to update_idletasks() fixes the issue. But we should investigate why all works on 3.5 and is there downside of this change. -- ___ Python tracker _

[issue20167] Exception on IDLE closing

Serhiy Storchaka added the comment: > In any case, the traceback makes no sense. Before > "self.color_breakpoint_text()" in __init__ are 3 "self.text.bind" > statements. So self.text = None seems implausible. The code runs up to self.text.update() in restore_file_breaks() and runs further only

[issue20167] Exception on IDLE closing

Terry J. Reedy added the comment: The above appears to be a system-specific open issue, not a close issue. So it must be a different issue. On my Win7 F:\Python\dev\4\py34\PCbuild>python_d -m idlelib ../Lib/decimal.py F:\Python\dev\4\py34\PCbuild> C:\Programs\Python34>python -m idlelib Lib/d

[issue20167] Exception on IDLE closing

Serhiy Storchaka added the comment: On 3.5 the issue is gone, but on 3.4 and 2.7 following traceback are generated: $ ./python -m idlelib.idle Lib/decimal.py Traceback (most recent call last): File "/home/serhiy/py/cpython-3.4/Lib/runpy.py", line 170, in _run_module_as_main "__main__", mo

[issue20167] Exception on IDLE closing

Serhiy Storchaka added the comment: > I forget how to get the third, micro number. tkinter.Tcl().call('info', 'patchlevel') -- ___ Python tracker ___ ___

[issue20167] Exception on IDLE closing

Terry J. Reedy added the comment: I know. 3.4.2.rc1 was released over 2 weeks ago and 3.4.2 just yesterday (essentially without change). So you have to delete space again. Since 3.4.1 worked for many people, perhaps you have an ancient version of tk. You can get major/minor number with >>>

[issue20167] Exception on IDLE closing

Rusi added the comment: On Fri, Oct 10, 2014 at 8:49 AM, Rustom Mody wrote: > On Fri, Oct 10, 2014 at 8:46 AM, Terry J. Reedy > wrote: >> >> Terry J. Reedy added the comment: >> >> I verified that problem had returned on Windows as well. It would be good >> to have a test that would fail if

[issue20167] Exception on IDLE closing

Rusi added the comment: On Fri, Oct 10, 2014 at 8:46 AM, Terry J. Reedy wrote: > > Terry J. Reedy added the comment: > > I verified that problem had returned on Windows as well. It would be good to > have a test that would fail if the tcl error message changed again. > > -- > resolutio

[issue20167] Exception on IDLE closing

Terry J. Reedy added the comment: I verified that problem had returned on Windows as well. It would be good to have a test that would fail if the tcl error message changed again. -- resolution: fixed -> stage: needs patch -> test needed versions: +Python 3.5 _

[issue20167] Exception on IDLE closing

Roundup Robot added the comment: New changeset ce0316007b21 by Terry Jan Reedy in branch '3.4': Issue #20167: revise condition to accomodate message change. https://hg.python.org/cpython/rev/ce0316007b21 -- ___ Python tracker

[issue20167] Exception on IDLE closing

Terry J. Reedy added the comment: The problem is the change in the exception message between these two lines can't invoke "bind" command: application has been destroyed can't invoke "bind" command: application has been destroyed In your copy of MultiCall.py, line 63-4, change APPLICATION_GONE =

[issue20167] Exception on IDLE closing

Rusi added the comment: Just confirming: idle 3.4.1-1 on debian testing Start idle3 Open recent file -> some file Close file Close interpreter (and idle) Get this Exception ignored in: > Traceback (most recent call last): File "/usr/lib/python3.4/idlelib/MultiCall.py", line 244, in __del__

[issue20167] Exception on IDLE closing

Terry J. Reedy added the comment: This has been left open to see if the undlying problem can be found. If #20567 is a guide, there might be a root.destroy that should be followed by del root. -- resolution: -> fixed stage: -> needs patch ___ Python

[issue20167] Exception on IDLE closing

Tal Einat added the comment: Good catches, Terry and Serhiy! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20167] Exception on IDLE closing

Roundup Robot added the comment: New changeset b9e124851e47 by Terry Jan Reedy in branch 'default': Issue #20167: Add missing else: break in 3 places as noticed by Serhiy. http://hg.python.org/cpython/rev/b9e124851e47 -- ___ Python tracker

[issue20167] Exception on IDLE closing

Serhiy Storchaka added the comment: Changes for _SimpleBinder.__del__ look doubtful. Any TclError exception is suppressed and "if" statement does nothing. Perhaps you forgot "else: raise"? And may be in other places too. -- ___ Python tracker

[issue20167] Exception on IDLE closing

Roundup Robot added the comment: New changeset f9f2c57f7d00 by Terry Jan Reedy in branch 'default': Issue #20167: Suppress 3.4 specific 'Exception ignored' messages. http://hg.python.org/cpython/rev/f9f2c57f7d00 -- nosy: +python-dev ___ Python tracker

[issue20167] Exception on IDLE closing

Terry J. Reedy added the comment: I checked that -m idlelib acts the same as -m idlelib.idle, and that there is still a problem after opening a second editor window after the original. So the messages seem tied to not opening a shell window. In testing the patch, I noticed that exceptions are

[issue20167] Exception on IDLE closing

Terry J. Reedy added the comment: More thoughts: The reason for explicit __del__ is to release memory resources connected to other objects or structures at the behest of the Python instance being deleted. If __del__ were only called at shutdown, it would not be needed, as all memory is release

[issue20167] Exception on IDLE closing

Terry J. Reedy added the comment: I tried all three versions both installed and recent repository builds and verified that the overt issue is limited to 3.4. I agree that the exception message suggests stopping with the first exception. Since there is a small cost to try: and break, I am incli

[issue20167] Exception on IDLE closing

Tal Einat added the comment: Both previous patches caused an import error. Here's a new patch with that fixed, and actually tested to fix the bug. -- Added file: http://bugs.python.org/file33927/taleinat_idle_closing_exception_3.patch ___ Python tra

[issue20167] Exception on IDLE closing

Tal Einat added the comment: Attaching second patch, to replace the first. As suggested by Serhiy, I moved the try/except block into the loop. I also added a comment explaining the try/except block and referencing this issue. -- Added file: http://bugs.python.org/file33926/taleinat_i

[issue20167] Exception on IDLE closing

Tal Einat added the comment: I put the try/except outside of the loop on purpose. If calling the widget's unbind() method fails once, it will fail forever afterwards. If you prefer a different spelling, move the try/except into the loop, and break out of the loop in case of an exception: for

[issue20167] Exception on IDLE closing

Serhiy Storchaka added the comment: 1. try/except should be inside a loop, not outside. 2. It would be better not to hide the problem under the rug, but find why the order of destruction is different when open shell window. Of course, if better solution will not be found, we will have to appl

[issue20167] Exception on IDLE closing

Tal Einat added the comment: This is caused by MultiCall's _ComplexBinder.__del__() being called during app shutdown. _ComplexBinder.__del__() unbinds a bunch of event handlers from the widget to which it is attached. It seems that there's some edge case here where the underlying Tk widget has

[issue20167] Exception on IDLE closing

Tal Einat added the comment: Confirmed on OSX 10.8 with Python 3.4 (built from default branch, changeset 88969:32af4954e46a). Note that this doesn't happen when opening just a shell window, e.g. by running ./python -m idlelib.idle. Furthermore, even when running IDLE as described in the OP, i

[issue20167] Exception on IDLE closing

New submission from Serhiy Storchaka: When run IDLE with file name as agument $ ./python -m idlelib.idle Lib/decimal.py and then close or exit it, following traceback is printed: Exception ignored in: > Traceback (most recent call last): File "/home/serhiy/py/cpython/Lib/idlelib/MultiCall.py