Text.edit_modified() fails because it calls _getints() on the 
result of the underlying tk.call().  The tk.call() is returning a 
boolean, not a string, and the _getints() fails.

Here's the last part of an example traceback:

File "/usr/local/src/staff/pett/chimera/devel/Ilabel/
__init__.py", line 53, in textCB
    if not text.edit_modified():
  File "/usr/local/src/staff/chimera-build/IRIX-X11/foreign/
Python-2.3.2/lib/python2.3/lib-tk/Tkinter.py", line 2831, in 
edit_modified
    return self.edit("modified", arg)
  File "/usr/local/src/staff/chimera-build/IRIX-X11/foreign/
Python-2.3.2/lib/python2.3/lib-tk/Tkinter.py", line 2819, in 
edit
    return self._getints(
  File "/usr/local/src/staff/chimera-build/IRIX-X11/foreign/
Python-2.3.2/lib/python2.3/lib-tk/Tkinter.py", line 972, in 
_getints
    return tuple(map(getint, self.tk.splitlist(string)))
TypeError: coercing to Unicode: need string or buffer, bool 
found

Logged In: YES 
user_id=1051353

I should mention that it's the argless form of edit_modified() that
fails (querying the flag state) -- setting the flag works.

followup from https://bugs.launchpad.net/bugs/84720



As a workaround you can get the status by calling:

print root.tk.call('eval','%s edit modified'%self.textwidget)

where self.textwidget is the variable where the text widget was assigned to.

Moved my patch from Issue1643641 to this Issue.
(duplication was created when moving from SF bugs/patches)
Patch to be applied with 'patch -p0'
I have also attached a demo where you can test
all Text.edit_* functions.

Regards,
Matthias Kievernagel

Retested revision 59927 from the trunk.
Error is still there, is demonstrated
by attached editModified.py (click 'modified?')
and patch is still applicable and corrects
the problem.

Regards,
Matthias Kievernagel

From issue 1362475:

This bug still exists, I'm attaching a patch against current python-trunk.
This patch is based on the fact that documentation tk 8.4 (version which
edit command was added) and tk 8.5 says only edit_modified is supposed
to return something, which is either 0 or 1, so there was no reason to
use _gettints on that tk.call, and returning an empty tuple is against
the expected value, 0.

--- cut ---

This message and patch is almost a duplicate of Matthias, just updating
from the just closed, and duplicated, issue 1362475

OK, committed patch as r63412.