classification
Title: Add after_info as a function to tkinter
Type: enhancement Stage: patch review
Components: Tkinter Versions: Python 3.8
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: csabella, serhiy.storchaka, terry.reedy
Priority: normal Keywords: patch

Created on 2018-02-13 13:38 by csabella, last changed 2018-02-16 13:24 by csabella.

Pull Requests
URL Status Linked Edit
PR 5664 open csabella, 2018-02-13 18:27
Messages (13)
msg312119 - (view) Author: Cheryl Sabella (csabella) * Date: 2018-02-13 13:38
In tkinter, after_cancel has a call to after info:
data = self.tk.call('after', 'info', id)

Since this is a supported command, there should be a function to access it directly.

https://www.tcl.tk/man/tcl8.6/TclCmd/after.htm
msg312123 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2018-02-13 14:30
What is the use case for this method? How it could be used?
msg312127 - (view) Author: Cheryl Sabella (csabella) * Date: 2018-02-13 15:24
I was working on the tests for issue32831.  One of the methods was `__del__` which made sure timer events were canceled with `after_cancel`.  In the test, to assert that the after events no longer existed after calling `__del__` and after reading the Tcl documentation for `after`, I tried to call `after_info` but it didn't exist. So I added a call to `self.tk.call('after', 'info', id)` directly to assert that the after events no longer existed.

I don't know if there is a general need to know whether timer or idle events exist, but this command gives that information.
msg312133 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2018-02-13 17:32
I'm not sure what after_info(id) should return.
msg312134 - (view) Author: Cheryl Sabella (csabella) * Date: 2018-02-13 18:29
I've made a pull request.  I understand that you may not want to add this functionality, but perhaps the docstring will answer your questions.  I took it from the Tcl docs page.
msg312142 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2018-02-13 22:45
I am in favor of exposing all of tk where it makes sense to do so, and I think it does here.

After 'translating' the tk after_info entry into tkinter-ese, I would expect and want that
  root.after_info(root.after(f, 100000))[0] is f
be true.  the same as would be true of the tcl equivalent. (This could even be a test.)  It appears that the current patch instead returns a (python) reference to the tcl wrapper of f.  The fact that python callbacks get wrapped as tcl callbacks is currently transparent to tkinter users and should remain so.

Serhiy, I presume that this is what you were uncertain about.  I am presuming above that f can be recovered.

Returning the function kind as 'timer' or 'idle' is fine. In other contexts, an enumeration would be a possibility, but this does not seem to fit tkinter.

I presume a bad id results in TclError.  Do other tkinter functions allow TclError to propagate?  My impression is no.  If so, it should be replaced here in a way consistent with other tkinter practice.
msg312159 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2018-02-14 06:46
On one side, the first item of the list returned by the Tcl command `after info $id` is a name of the Tcl command generated by Tkinter. It is internal, it was not exposed to Tkinter users before, and the API for restoring the original Python callable is private.

On other side, `after info` can return not only events created by Tkinter, but events created by Tcl (either by direct execution of Tcl script, this is still can be useful with programming with Tkinter, or created by the Tcl standard library or third-party Tcl libraries). In that case a Python callable can't be returned.

This is what I was uncertain about. Maybe after_info() should return a Python callable if possible, and keep the original result otherwise? This complicates its implementation and definition.

TclError is legal and expected. In some methods it is caught, either because the method is purposed to be called at widget destroying stage, when the order of different cleanup procedures is not specified, and Tcl names can be destroyed before destroying Tkinter wrappers, or because the method was implemented differently in the past, and catching TclError is needed for backward compatibility. after_info() is not the case.
msg312160 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2018-02-14 06:57
Note that in the tests for issue32831 you need to use call('after', 'info') if you want to backport them.
msg312177 - (view) Author: Cheryl Sabella (csabella) * Date: 2018-02-14 16:39
>>> It is internal, it was not exposed to Tkinter users before, and the API for restoring the original Python callable is private.

I thought `bind(sequence)` also returned these internal Tcl function names?  For example, if I do a print on the set_breakpoint_here text widget in IDLE, it prints :
if {"[140358823678376set_breakpoint_here %# %b %f %h %k %s %t %w %x %y %A %E %K %N %W %T %X %Y %D]" == "break"} break


In order for it to return the python function name, I think the `after` function would need to write to a dictionary of `name: func` where name is currently used as the Tcl function name that is registered?  Is there something in tkinter that does this now that it could be modeled from?  Since events are removed from Tcl once that are invoked, how would the dictionary be cleaned up?  Would after_info need to be polled every once in a while to clean up the dictionary or would it just exist until the object is destroyed?
msg312191 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2018-02-15 02:21
A person who can create a tcl callback with tk.call can inquire with tk.call('after', 'info', id).  That does not cover callbacks created by tcl or extensions thereof, but references to such callbacks are unlikely to be useful to anyone who does not know any tcl.

I see these choices for after_info(id):

A. Return the tcl script reference even when it wraps a python function.  I don't like this, as the tcl reference is useless to most people.

B. Convert the reference to a Python function if possible but return it if not.  This is a bit awkward to document and any use requires a type check.  Having a function return such different types, depending on the input, is frowned upon.

C. Convert the reference to a function if possibe and raise TypeError or ValueError is not.  This is incomplete but easier for a pure Python programmer to deal with.  The documentation could specify how those who want a tcl reference can get it.

D. Don't implement after_info(id), at least not now, and just after_info().  Information about the current existence of a callback is contained in the list returned by after_info().  Each of the following pairs should be equivalent:

  assertIn(id, after_info())
  assertEqual(len(after_info(id)), 2)

  assertNotIn(id, after_info())
  assertRaises(TclError, after_info, id)

(For testing after_info(), assertIn and assertNotIn avoid assuming that tcl does not add any internal callbacks.)
msg312198 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2018-02-15 10:22
> Since events are removed from Tcl once that are invoked, how would the dictionary be cleaned up?  Would after_info need to be polled every once in a while to clean up the dictionary or would it just exist until the object is destroyed?

Good question. Currently the reference to a callable is kept in the dict  until the object is destroyed. This can be considered as a bug (see issue1524639).
msg312199 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2018-02-15 10:30
I agreed with Cheryl's conclusion that likely after_cancel() had been called with None. The comments about 8.4 is wrong, and the solution in issue763637 is not correct. The current code code deletes the script for the first event if pass None to after_cancel(). Do you ming to open a PR for proper solving issue763637 Cheryl?
msg312232 - (view) Author: Cheryl Sabella (csabella) * Date: 2018-02-16 13:24
I created issue32857 for the after_cancel issue.  Thanks!
History
Date User Action Args
2018-02-16 13:24:06csabellasetmessages: + msg312232
2018-02-15 10:30:48serhiy.storchakasetmessages: + msg312199
2018-02-15 10:22:53serhiy.storchakasetmessages: + msg312198
2018-02-15 02:21:54terry.reedysetmessages: + msg312191
2018-02-14 16:39:26csabellasetmessages: + msg312177
2018-02-14 06:57:09serhiy.storchakasetmessages: + msg312160
2018-02-14 06:46:08serhiy.storchakasetmessages: + msg312159
2018-02-13 22:45:06terry.reedysetmessages: + msg312142
2018-02-13 18:29:31csabellasetmessages: + msg312134
2018-02-13 18:27:54csabellasetkeywords: + patch
stage: patch review
pull_requests: + pull_request5466
2018-02-13 17:32:17serhiy.storchakasetnosy: + terry.reedy
messages: + msg312133
2018-02-13 15:24:16csabellasetmessages: + msg312127
2018-02-13 14:30:53serhiy.storchakasetnosy: + serhiy.storchaka
messages: + msg312123
2018-02-13 13:38:15csabellacreate