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 idiscovery
Recipients
Date 2002-11-19.21:27:20
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=33229

That's right: Tkinter silently discards all background Tcl
errors. 

All errors from Tcl are silenced by def _tkerror(err): pass
So Tkinter users will never see any errors that come from
any bugs in Tcl, Tk or its extensions, including of course
errors that may only show up under Python.

The proposed solution for this problem is simply to
remove the createcomand / def _tkerror. I see no possible
reason for it to be in there, and it violates the
fundamental principle that errors should be raised and dealt
with.

Although Tkinter behaved that way since the beginning, the
change takes backwards compatibility into account because
it serves no good purpose that I know of to begin with. At
worst buried bugs will become visible and can be dealt with.
History
Date User Action Args
2008-01-20 09:55:48adminlinkissue639266 messages
2008-01-20 09:55:48admincreate