After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 626384 - Re-introduce iterable models and indexable rows
Re-introduce iterable models and indexable rows
Status: RESOLVED DUPLICATE of bug 631547
Product: pygobject
Classification: Bindings
Component: introspection
2.21.x
Other Linux
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-08 18:55 UTC by Mathias Brodala
Modified: 2010-10-09 15:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mathias Brodala 2010-08-08 18:55:06 UTC 
The ability to iterate through GtkTreeModel should be ported to GI as override. And so should indexable GtkTreeRowReference to again allow for easy access via row[row][column].

BTW: For custom models GtkTreeModel should be derived from, as there is nothing equivalent to gtk.GenericTreeModel in GI?
Comment 1 Holger Berndt 2010-10-08 08:18:36 UTC 
That I can't just do stuff like

for row in liststore:
    row[0] = "foo"

is actually not only an inconvenience for me, but has rather deep impact. I am using Python'esque duck-typing, so most parts of my code (and possibly plugins) don't even know that a particular object is e.g. a GtkListStore - they just expect to be able to treat it like above. Functions might sometimes get a ListStore, sometimes just a list of lists - they don't (and shouldn't have to) care.
Comment 2 Sebastian Pölsterl 2010-10-09 15:21:44 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 631547 ***