Comment 9 for bug 1012703

Am Mittwoch, den 13.06.2012, 22:24 +0000 schrieb Matthias Klumpp:
> Hi!
> This doesn't look sane to me... If you want to use PackageKit in your application, please use the GIR from Python3, there is no supported version of official Python bindings for PackageKit.
> The python-packagekit package is (and should be) only used by backends, client applications need to use the GIRepository.
> However, I'll look into the code to see if PK is Py3 compatible (I think it is) and if there's stuff remaining which needs to be done. (we had a few patches for Py3 some weeks ago...)
> (Maybe we could even drop the python-packagekit with new releases? - Need to find out more about it...)

Dropping python-packagekit isn't an option. The python-packagekit
package is required by the apt and smart backend. Furthermore it is used
by aptdaemon and the plugins which are available for the apt backend and
aptdaemon (language-selector, ubuntu-driver-common, etc).

AFAIK Smart isn't yet ported to Python 3 so the backend will require
Python 2 for a longer period of time.

The apt backend should actually by Python 3 compatible (except a to be
changed import) but it hasn't worked when I gave it a short look. Needs
some investigation.

language-selector and ubuntu-drivers-common are not only PackageKit
clients: aptdaemon and the apt backend share a plugin system which
allows to modify the dependency resolver and to add WhatProvides
handlers. So language-selector modifies the resolver to ensure that the
language packs for non-default applications get installed and
ubuntu-drivers-common provide mod aliases/driver resolution.