On Sat, Jan 22, 2011 at 16:27, Piñeiro <[email protected]> wrote: > From: Tomeu Vizoso <[email protected]> > >> On Fri, Jan 21, 2011 at 17:22, Piñeiro <[email protected]> wrote: >>> >>> So my question (please, if there are a best ml, point that, AFAIK, >>> there isn't a gobject introspection mailing list): >>> >>> * There is a way to force to "load the old python bindings" when you >>> call "import gconf" ? >> >> The problem here is that the python classes that wrap GType types are >> kept in a cache indexed by GType. This means that whatever wrapper for >> a given GType gets loaded the first will stick for the rest of the >> life of the process. >> >> See http://git.gnome.org/browse/pygobject/tree/gobject/pygobject.c#n891 >> >> We could do some hacks to workaround this but given that pygtk are the >> only supported bindings for gtk+2 and pygobject+introspection are the >> only supported bindings for gtk+3, probably python modules in GNOME >> should keep separate branches depending on the gtk+ version they are >> supposed to work with. > > Ok, thank you very much for the information. As far as I undertand > you, in the specific case of pyatspi2, it would be required to > maintain a non-pygobject-introspection version for the apps still > using gtk+2, and use the current pygobject+introspection based on > master for apps using gtk+3 (so, ported to pygobject+introspection). > > Right=
Yes, that's the only supported scenario AFAIK. Regards, Tomeu > BR > > === > API ([email protected]) > _______________________________________________ > gtk-devel-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/gtk-devel-list > _______________________________________________ gnome-accessibility-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
