desktop-packages team mailing list archive

[Fabien LOISON <flo@xxxxxxxxxxxxx>]

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...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/859104

Title:
  Nautilus extensions written in Python do not work in Oneiric

Status in “arista” package in Ubuntu:
  New
Status in “arkose” package in Ubuntu:
  New
Status in “bzr-gtk” package in Ubuntu:
  New
Status in “groundcontrol” package in Ubuntu:
  New
Status in “kupfer” package in Ubuntu:
  New
Status in “nautilus” package in Ubuntu:
  Invalid
Status in “nautilus-clamscan” package in Ubuntu:
  New
Status in “nautilus-image-manipulator” package in Ubuntu:
  Confirmed
Status in “nautilus-pastebin” package in Ubuntu:
  New
Status in “nautilus-python” package in Ubuntu:
  New
Status in “postr” package in Ubuntu:
  New
Status in “rabbitvcs” package in Ubuntu:
  New
Status in “sparkleshare” package in Ubuntu:
  New
Status in “tortoisehg” package in Ubuntu:
  Confirmed
Status in “nautilus-python” package in Debian:
  New

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.

  [0] https://bugs.launchpad.net/ubuntu/+source/nautilus-image-manipulator/+bug/849361
  [1] https://bugs.launchpad.net/ubuntu/+source/nautilus-python/+bug/858925

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arista/+bug/859104/+subscriptions