This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author taleinat
Recipients kbk, roger.serwy, serhiy.storchaka, taleinat, terry.reedy
Date 2014-02-05.10:33:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391596403.34.0.274055617224.issue20167@psf.upfronthosting.co.za>
In-reply-to
Content
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 already been destroyed.

Instead of trying to debug all of the Tk events and app shutdown order, I propose just surrounding this __del__() code with a try/except block, catching _tkinter.TclError and ignoring it. From my (somehwat limited) understanding of MultiCall, this shouldn't do any harm.

See attached patch.
History
Date User Action Args
2014-02-05 10:33:23taleinatsetrecipients: + taleinat, terry.reedy, kbk, roger.serwy, serhiy.storchaka
2014-02-05 10:33:23taleinatsetmessageid: <1391596403.34.0.274055617224.issue20167@psf.upfronthosting.co.za>
2014-02-05 10:33:23taleinatlinkissue20167 messages
2014-02-05 10:33:23taleinatcreate