GNOME Bugzilla – Bug 672087
Add bw-compatible arguments to Gtk.Adjustment
Last modified: 2012-03-16 19:41:24 UTC
The argument used to be called page/step_incr, if they are found map them to the existing properties for extra compatibility.
Created attachment 209768 [details] [review] Add bw-compatible arguments to Gtk.Adjustment
Review of attachment 209768 [details] [review]: Looks good to me... I wonder if this level of compat could be a slippery slope, but let's add it, if it grows too much we can revisit the decision
FWIW, I'd much rather not have this, and instead add that renaming to pygi-convert.sh. We really should not proliferate such arbitrary renamings and C API breakage in PyGI.
My usecase prevents me from using pygi-convert.sh, it's only one of the possible migration strategies for PyGTK->PyGI. I propose that this goes in, since I have code that depends on that and I think it would be useful for others. After the next release, we'll start moving this and some other PyGTK specific APIs to pygtkcompat.py and leave this as is, would that be okay?
Attachment 209768 [details] pushed as 680a2e0 - Add bw-compatible arguments to Gtk.Adjustment