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 serhiy.storchaka
Recipients serhiy.storchaka, terry.reedy
Date 2016-06-28.08:05:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1467101160.96.0.000959009774067.issue27405@psf.upfronthosting.co.za>
In-reply-to
Content
For debugging purpose it would be helpful to have an ability to show all Tcl commands executed by Tkinter. In particular it would be helpful for testing wherever some issue is Tkinter issue or Tcl/Tk issue.

I'm working on a patch, but there is a design question about an interface.

In simplest case you set the debug property of Tk instance to True and all Tcl commands are printed to stdout or stderr in the form ready for executing with Tcl/Tk interpreter. You also can set the module global tkinter.debug to True, and this will affect all new Tk instances (as with tkinter.wantobjects).

But maybe there is a need in larger customization? For example specifying the command that accepts every Tcl command as a string or a tuple?
History
Date User Action Args
2016-06-28 08:06:01serhiy.storchakasetrecipients: + serhiy.storchaka, terry.reedy
2016-06-28 08:06:00serhiy.storchakasetmessageid: <1467101160.96.0.000959009774067.issue27405@psf.upfronthosting.co.za>
2016-06-28 08:06:00serhiy.storchakalinkissue27405 messages
2016-06-28 08:05:59serhiy.storchakacreate