Bug 788545

Summary: GtkTreeModel.iter_previous and iter_next have confusingly different behaviour
Product: [Fedora] Fedora Reporter: Vratislav Podzimek <vpodzime>
Component: pygobject3Assignee: John (J5) Palmieri <johnp>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: icq, jkeck, johnp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-20 06:40:10 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Vratislav Podzimek 2012-02-08 07:17:05 EST
Description of problem:
While GtkTreeModel.iter_next(itr) has an override and does not modify itr, iter_previous(itr) modifies it. Since both these functions behave in the same way in the original C code I would expect this also in the Python gi binding.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. try to use iter_next(itr) and iter_previous(itr) from Python and see what's happening to itr
Actual results:
confusing difference in behaviour

Expected results:
no confusing difference -- preserving itr in both cases would be better
Comment 1 Vratislav Podzimek 2012-10-20 06:40:10 EDT
This is fixed in recent rawhide versions.