[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Changes to Tk 8.4 breaking Tkinter?



Hi,

I maintain the 'uligo' package, which uses Tkinter. Since recently (I'm
not sure exactly when; it worked when I uploaded it but doesn't work
now...), Tkinter has been throwing an exception when moving the mouse
over the game board or clicking:

Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/lib/python2.2/lib-tk/Tkinter.py", line 1299, in __call__
    args = apply(self.subst, args)
  File "/usr/lib/python2.2/lib-tk/Tkinter.py", line 1032, in _substitute
    e.num = getint(b)
ValueError: invalid literal for int(): ??

It seems __call__ in the CallWrapper class (which is internal to Tk) is
getting called with arguments like:

('3669', '??', '??', '??', '??', '16', '553755622', '??', '147', '407',
'??', '0', '??', '??', '.139284980.139677068.139366564', '6', '348',
'480', '??')

_substitute is then trying to convert the second argument (which I think
is supposed to be an event number) to an integer, which fails. If that
had succeeded, it would've tried to convert several other arguments to
integers, which also would've failed.

Unfortunately, my Tk-fu is nonexistent. Can anyone pinpoint where this
bug is (uligo, Tkinter, Tk 8.4?) I think it's an incompatibility between
Tkinter and Tk 8.4, but I'm not sure.
-- 
Joe Wreschnig <piman@debian.org>

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: