Hi Ignacio, 2014-02-17 9:35 GMT-03:00 Ignacio Rodríguez <nachoe...@gmail.com>: > Sorry, but was about: > >>>> import test2
I think importing the module can have unpredictable results. >>>> hasattr(test2, "gtk") > True >>>> hasattr(test2, "Gtk") > False >>>> > > If "Gtk" this return True >>>> import test3 >>>> hasattr(test3, "gtk") > False >>>> hasattr(test3, "Gtk") > True >>>> > > > Just a idea > > Saludos. > Ignacio Rodríguez > > > 2014-02-17 10:31 GMT-02:00 Gonzalo Odiard <godi...@sugarlabs.org>: >> >> This is a reply to @dnarvaez comment >> >> >> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/104#issuecomment-35170356 >> >> The addition of a field to identify gtk2/gtk3 activities, >> was proposed as a solution to View Source issue [1] >> >> I think there are two other easier ways to solve this particular issue: >> >> * check the setup.py file >> * check the file with the startup class (view source already identify the >> file, see [2] >> >> Making changes to the activity.info file usually take a long time >> to get included in a significant number of activities, >> if we can solve it in the code is better in my opinion. >> >> -- >> Gonzalo Odiard >> >> SugarLabs - Learning Software for children >> >> [1] >> https://github.com/sugarlabs/sugar-toolkit-gtk3/pull/104#issuecomment-35170356 >> [2] >> https://github.com/sugarlabs/sugar/blob/master/src/jarabe/view/viewsource.py#L205 >> >> _______________________________________________ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- .. manuq .. _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel