[issue27405] Ability to trace Tcl commands executed by Tkinter

Cheryl Sabella added the comment: Seems like this didn't make 3.7. Would it be good to make a PR targeting 3.8? -- nosy: +cheryl.sabella ___ Python tracker ___

[issue27405] Ability to trace Tcl commands executed by Tkinter

Ned Deily added the comment: Let's target it for 3.7 and when it is ready we can discuss whether to backport it to 3.6 as well. -- versions: +Python 3.7 -Python 3.6 ___ Python tracker

[issue27405] Ability to trace Tcl commands executed by Tkinter

Serhiy Storchaka added the comment: This feature is useful first at all for us, core developers. I think we could add it with provisional status in the beta stage or wait to 3.7. In any case the documentation and tests are not ready yet. -- nosy: +ned.deily

[issue27405] Ability to trace Tcl commands executed by Tkinter

Terry J. Reedy added the comment: If not in 3.6, I can still apply patch from shelf, recompile, use for awhile, re-shelve, recompile. So not tragedy if miss deadline. -- ___ Python tracker

[issue27405] Ability to trace Tcl commands executed by Tkinter

Terry J. Reedy added the comment: I ran idle and tcl/tk/ttk tests. all pass with and without patch. text_tcl before and with patch ends with warning: Windows fatal exception: access violation. I have seen this for perhaps a couple of weeks (check windows buildbot), but not forever. You

[issue27405] Ability to trace Tcl commands executed by Tkinter

Terry J. Reedy added the comment: Much better. I can more or less follow IDLE startup. >>> import tkinter >>> tkinter.debug False >>> tkinter.debug = True >>> import idlelib.idle proc tkerror {} {} proc exit {} {} proc 27305592destroy {} {>} wm protocol . WM_DELETE_WINDOW 27305592destroy wm

[issue27405] Ability to trace Tcl commands executed by Tkinter

Terry J. Reedy added the comment: The patch changes 4 non-tkinter clinic files. Accident? All 4 are rejected. Will compile and test tkinter changes. -- ___ Python tracker

[issue27405] Ability to trace Tcl commands executed by Tkinter

Serhiy Storchaka added the comment: Here is more mature patch. Now you can set tracing function with the tkinter.Tk.settrace() method. Tracing function takes the single argument -- a tuple containing the command and arguments. If set global tkinter.debug to True, the tracing function of newly

[issue27405] Ability to trace Tcl commands executed by Tkinter

Terry J. Reedy added the comment: I just noticed that the patch includes a patch to _tkinter.c, which however, does not show up on the Rietveld dashboad, where I first reviewed it. Sorry for the mistaken comment. -- ___ Python tracker

[issue27405] Ability to trace Tcl commands executed by Tkinter

Serhiy Storchaka added the comment: You need to recompile the _tkinter module. -- ___ Python tracker ___ ___

[issue27405] Ability to trace Tcl commands executed by Tkinter

Terry J. Reedy added the comment: In "debug = False+1', I presume the '+1' is just temporary. The debug property and the clinic file refer to _tkinter.tkapp.get/settrace, which do not exist. Did you just forget to include that part? Or does 'preliminary' mean 'do not test yet'? >>> import

[issue27405] Ability to trace Tcl commands executed by Tkinter

Serhiy Storchaka added the comment: Here is preliminary patch. It contains leaks, don't worry. -- keywords: +patch Added file: http://bugs.python.org/file43592/tkinter_trace_tcl.patch ___ Python tracker

[issue27405] Ability to trace Tcl commands executed by Tkinter

Serhiy Storchaka added the comment: I meant adding API similar to sys.settrace() for specifying a function that will be called before executing every Tcl command. -- ___ Python tracker

[issue27405] Ability to trace Tcl commands executed by Tkinter

New submission from Serhiy Storchaka: 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