I'm having an issue with the InfoProvider methods. The update_file_info function passes several parameters to the extensions, that they need to keep track of in order to be used asynchronously. One is the NautilusOperationHandle struct and the other is the update_complete closure. I'll talk first about the handle.
For the NautilusOperationHandle, I'm importing the Nautilus.OperationHandle attribute from the gi.repository.Nautilus module and assigning it to the PyObject, which I then convert all incoming handles to from their C counterparts. The problem is that when the python extension tries to pass the handle to the Nautilus.info_provider_update_complete_invoke function, I get the following error: Traceback (most recent call last): File "/home/aplumb/.local/share/nautilus-python/extensions/update-file-info-async.py", line 17, in update_cb Nautilus.info_provider_update_complete_invoke(self.hello, provider, handle, Nautilus.OperationResult.FAILED) File "/usr/lib/python2.7/site-packages/gtk-2.0/gi/types.py", line 40, in function return info.invoke(*args) TypeError: argument 2: Must be Nautilus.OperationHandle, not StructMeta I'm having a problem with the closure stuff too but I figured I would start with this. Adam On Thu, Mar 10, 2011 at 11:35 PM, Cosimo Cecchi <cosi...@gnome.org> wrote: > On Tue, 2011-03-08 at 16:23 -0500, Adam Plumb wrote: >> I finally made some progress getting the nautilus-python bindings >> updated to work with gobject introspection and without pygtk. They >> take advantage of the fact that Nautilus publishes its annotations in >> the gi repository. That has the great benefit of allowing >> nautilus-python to finally shed it's defs and overrides files, and to >> remove its dependency on pygtk. > > Hi Adam, > > this is good news! Please file bugs if you find missing annotations in > libnautilus-extension. > > Thanks, > > Cosimo > > -- nautilus-list mailing list nautilus-list@gnome.org http://mail.gnome.org/mailman/listinfo/nautilus-list