On Wed, May 11, 2011 at 10:05 PM, Mikkel Kamstrup Erlandsen <[email protected]> wrote: > I think the underlying problem is that the interface is defined as async > in the Vala code (of lp:libunity). This is no problem at all in Vala, > and only a minor inconvenience in C, but with GI-bound languages such as > Python this may become a problem (or in the specific case of PyGI we now > *know* it's a problem). > > I can't recall exactly why it was made async originally, but of the top > of my head I can't think of any reason it needs to be that way. So maybe > file a bug against libunity (also add a task on unity itself) requesting > that the method be converted into a normal synchronous ala: > > UnityActivationStatus activate (const gchar *uri); > > Libunity will have to see some breakage for Oneiric anyway, so this one > may as well go with it.
Alright, I filed a bug against libunity: https://bugs.launchpad.net/libunity/+bug/781650 Regards, Johannes _______________________________________________ Mailing list: https://launchpad.net/~ayatana-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~ayatana-dev More help : https://help.launchpad.net/ListHelp
