Bug Description

This bug report is intended to serve as a meta to survey the state of the different Nautilus extensions written in Python in Ubuntu 11.10.

I have first noted that nautilus-image-manipulator does not show up when right-clicking on an image in Ubuntu 11.10, which it should (and does in Debian testing, where the package comes from).

Looking at the release notes, significant changes have been made to Nautilus-Python in versions 0.7 and 1.0 that change the paths where the extensions are to be looked in. Ubuntu 11.10 is the first Ubuntu version to use Nautilus-Python > 0.7, so I'm suspecting this affects all Nautilus extensions written in Python.

I have opened 2 bug reports that are relevant to this issue [0] and [1]. I suspect the problem is related to 2 things:
- The extensions are not looked for anymore in the familiar /usr/lib/nautilus/extensions-2.0/python
- Importing the module `nautilus` is not valid anymore

Please mark your project/package as affect by this bug so that we can keep track of the affected packages, and share the solution to fix this. Don't forgot to add a comment to this bug when doing so.

I originally planned to send the following email to all the projects listed at the bottom, but it turns out to be more complicated than I thought, between the larger projects that have maintainer groups, and individuals without a public email address. I am thus going to add the projects as being affected by this bug, if not you can change the status of this bug for your own program.

Subject: About your Nautilus extension being [probably] broken in Ubuntu 11.10
To: All developers of Nautilus scripts written in Python

Body:
Hi all,

I'm sending you this email since you are developing a Nautilus extension in Python that is available in Ubuntu 11.10 (list of such packages at the end of this email).
I have created such an extension myself and packaged it for Debian. It is available there in the "testing" version [0]. The extension installs correctly in Debian. However, the extension does not show up in Nautilus in Ubuntu 11.10 (beta 2 for now) (exact same version as in Debian).

These are the version of Nautilus-Python/Python-Nautilus that are packaged:
- In Debian: 0.6.1 [1]
- In Ubuntu 11.10: 1.0 [2]

Looking at the release notes, significant changes have been made in versions 0.7 and 1.0 that change the paths where the extensions are to be looked in.

I have opened 2 bug reports that are relevant to this issue [3] and [4]. I suspect the problem is related to 2 things:
- The extensions are not looked for anymore in the familiar /usr/lib/nautilus/extensions-2.0/python
- Importing the module `nautilus` is not valid anymore

I have installed various of your extensions, all of which failed to display in Nautilus. I suspect that a lot (all?) of the Nautilus extensions written in Python are currently broken in Ubuntu 11.10. Have you tested your packages in the latest Ubuntu Beta, before your regular users start opening bug reports? This is the reason for the broad list of recipients.

I have opened a bug report against Nautilus-Python [5] for us to track the extent of this issue, and hopefully find a solution for it. Please mark your project/package as affected by this bug (by using the "Also affects distribution" link) so that we can keep track of the affected packages, and share the solution to fix this. Don't forgot to add a comment to this bug when doing so.

I should now have added all source packages depending on nautilus-python in Ubuntu 11.10. Please add a post and update the status of the bug for your project if you determine it is not affected. Oh, and sorry for the eventual spam...

Andrew, just to make sure there's no misunderstanding, I marked Nautilus (itself) affected because the libnautilus-extension1 package (part of Nautilus) depends on python-nautilus. Are you sure this package is not affected?

Summary of the situation with Nautilus Python:
============================================

Moving to Nautilus 3.0 => Nautilus Python 1.0.0:

All the extensions have to be rewritten in GTK3 because Nautilus is
GTK3 now (so no more PyGTK). But we must continue to
use GObject 2.x (import gobject) because Nautilus Python still uses
gobject 2 ...
There is also a change to make for the path where the extension goes.

Move to Nautilus 3.2 (the one in Oniric) => [no Compatible version of
Nautilus Python]

The use of GObject 2 is no longer possible in Nautilus
because it conflicts with GObject 3... We must therefore modify Nautilus
Python (this is what Vincent Untz did in his patch). And we must
also modify the Python extensions (from gi.repository import
GObject,...).

So we have currently different problems to solve:
==================================================

* Nautilus Python must be patched or we can not
do anything. [The work is in progress for this part]

* Extensions must all be changed in one way or
another to make them work again (it is necessary to warn
the developers of the various extensions, and hope they
are willing to adapt their extensions (because it can be a huge
work for some extensions). I think that this will take
the most time...