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 cheryl.sabella
Recipients cheryl.sabella
Date 2018-02-16.13:20:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1518787214.25.0.467229070634.issue32857@psf.upfronthosting.co.za>
In-reply-to
Content
This was discovered while working on issue32839.  An old comment added for issue763637 resulted in further research and it was determined that the comment:

!             data = self.tk.call('after', 'info', id)
!             # In Tk 8.3, splitlist returns: (script, type)
!             # In Tk 8.4, splitlist returns: (script,)

wasn't correct.  The underlying difference is that the call to 'after info' returns different results depending on the way it's called.  If it's called with an 'id', it will return a tuple of (script, type) if the id is valid or a TclError if the id isn't valid.  However, if id is None, then 'after info' returns a tuple of all the event ids for the widget.  In the case of the original bug in issue763637, the reported message shows the return value of `('after#53',)`, which is definitely an after event id and not a (script,) tuple.

Serhiy mentions on issue32839 that the current code also deletes the script for the first event if after_cancel is called with None.
https://bugs.python.org/issue32839#msg312199
History
Date User Action Args
2018-02-16 13:20:14cheryl.sabellasetrecipients: + cheryl.sabella
2018-02-16 13:20:14cheryl.sabellasetmessageid: <1518787214.25.0.467229070634.issue32857@psf.upfronthosting.co.za>
2018-02-16 13:20:14cheryl.sabellalinkissue32857 messages
2018-02-16 13:20:14cheryl.sabellacreate