GNOME Bugzilla – Bug 138576
gtk.IconSet now has 2 constructors in gtk.defs, while only gtk_icon_set_new_from_pixbuf should be in this role
Last modified: 2004-12-22 21:47:04 UTC
Currently in CVS HEAD, gtk_icon_set_new and gtk_icon_set_new_from_pixbuf are both marked as contructors of gtk.IconSet in gtk/gtk.defs, causing gtk_icon_set_new to be set to the tp_init field of gtk.IconSet. This makes "gtk.IconSet(pixbuf)" fail with TypeError, while it was accepted in earlier versions of pygtk. The gtk.IconSet contructor should be implemented by _wrap_gtk_icon_set_new_from_pixbuf() in gtk/gtk.override, as it accepts the optional pixbuf argument covering both the no argument and new_from_pixbuf use cases. gtk_icon_set_new was marked as a constructor of gtk.IconSet in gtk.defs revision 1.140 -> 1.141 by xordoquy along with many gtk2.4 api additions. Attached patch to only mark gtk_icon_set_new_from_pixbuf as contructor.(A long winded bug report for a one line patch, I know ...).
Created attachment 26130 [details] [review] patch for gtk.IconSet contructor
Xavier, is this sort of regression `normal', or should we put some sort of verification in the defs generator scripts?
Fixed in CVS.