dogtail-devel [Bug 537954] New: No valid equality check for nodes

["dogtail (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=537954

  dogtail | Framework | Ver: 0.6.1
           Summary: No valid equality check for nodes
           Product: dogtail
           Version: 0.6.1
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: Framework
        AssignedTo: dogtail-maint gnome bugs
        ReportedBy: ydirson altern org
         QAContact: dogtail-maint gnome bugs
     GNOME version: Unspecified
   GNOME milestone: Unspecified


If I walk down the tree and memorize a well-identified set of nodes, and later
try to compare the results of a findChildren() call to those well-known nodes,
I realize they do not match, despite .blink() really showing the same (text
entry) widget:

- the objects do not have the same id(), which is surprising in itself, showing
that there is a waste of RAM by object duplication, so 'a is b' does not work
- 'a == b' does not work either

Maybe __cmp__ could be implemented for Node objects, so at least 'a == b' can
be used, but it would seem much better to me to avoid the duplication of
objects in RAM (although that might be an issue in python-atspi or even in
atk).

Even if fixing an underlying lib is the best long-term solution, it may be
useful to implement __cmp__ so dogtail can work with any version of the
to-be-fixed lib.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=537954.