GNOME Bugzilla – Bug 724275
Automatically call g_initable_init for classes which implement GInitable
Last modified: 2018-01-10 20:37:51 UTC
As noted in the GInitable docs [1] we should call g_initable_init after g_object_newv possibly in pygobject_init [2] or pygobject_constructv. This came up when reviewing overrides for Ggid where the "init" is being called manually from Python (bug 724009). [1] https://developer.gnome.org/gio/2.38/GInitable.html#GInitable.description [2] https://git.gnome.org/browse/pygobject/tree/gi/pygobject.c?id=3.11.5#n1302
Created attachment 275911 [details] [review] build: Reorganize package configuration and setup Cleanup package dependency checks for glib, gobject, gio, gi, and ffi. Add dependency on gio for GInitable usage in upcomming patch. Add required and private package dependency vars to configure.ac for re-use in pygobject-3.0.pc.in.
Created attachment 275912 [details] [review] Call g_initable_init in GObject initializer Add a call to g_initable_init in GObject initializer if the GObject implements the GInitable interface.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/pygobject/issues/66.