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 egnor
Recipients
Date 2002-02-24.17:49:25
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=128950

I *think* external access to the tcl_lock would do it (it's
been a while).  There are a bunch of helper functions/macros
inside the Tkinter code for handling this situation;
exposing and documenting those would be ideal.

As far as error reporting, I don't think that suffices. 
(Again, it's been a while.)  The problem is that the
exception is returned to the C side, which must figure out
what to do with it.  Specifically, the Tcl event loop should
be stopped and the exception reported to whoever invoked
it... but there's no direct way to stop the Tcl event loop.
 (Fuzzy memories here.)
History
Date User Action Args
2007-08-23 13:55:50adminlinkissue452973 messages
2007-08-23 13:55:50admincreate