Bug 1014559 - Update PackageKit to Python 3
Summary: Update PackageKit to Python 3
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 22
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
Depends On: PY3DNF
Blocks: F23PYTHON3
TreeView+ depends on / blocked
Reported: 2013-10-02 10:53 UTC by Miro Hrončok
Modified: 2015-03-11 08:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-03-10 22:17:27 UTC
Type: Bug

Attachments (Terms of Use)

Description Miro Hrončok 2013-10-02 10:53:54 UTC
Hi, we would like to use Python 3 on the default installation instead of Python 2 on Fedora 22.

From that perspective, your package is considered as IMPORTANT - that means, is has to be updated to Python 3, for our intention come true.

The goal here is, that this package uses Python 3 as default in Fedora 22.

Please, help use update to Python 3 flawlessly.

Check if upstream already support Python 3, if yes, use it and add te support to the package.

If upstream doesn't support Python 3 yet, encourage it to do so by sending patches and offering your help.

When upstream is dead or unwilling to support Python 3, you'll need to patch this package on Fedora level. Try to avoid this as much as you can, but use it, if it's the last option.

Chances are, that you ARE the upstream. In that case, everything is easier, just do it yourself.

Once Python 3 is supported, check your package, if it works with it. Don't switch to Python 3 yet as a default (that's still against the guidelines). I recommend to prepare your spec and conditionalize the thing with something like %global default_python 2/3.

There is a table on wiki, that should list your package. Chances are, that you can see an upstream link that covers the problem. Anyway, please update the table with information you know.


I offer my help with this task, so if you have no idea, how to work on this, or it is just not your priority, don't hesitate to ask for help.

(As you've already realized, this is a bulk text, so if something is not quite exact about your package, sorry for that, just ask)

Comment 1 Miro Hrončok 2013-10-02 11:29:40 UTC
This also means that all yum bindings should use dnf.

Comment 2 Toshio Ernie Kuratomi 2013-10-02 22:27:07 UTC
Note: do not follow this portion of the advice as it is against the Packaging Guidelines: "When upstream is dead or unwilling to support Python 3, you'll need to patch this package on Fedora level. Try to avoid this as much as you can, but use it, if it's the last option."

If you are in this situation, you'll essentially be forking upstream in order to produce a python3 port.  In that situation, the proper thing to do is to create a new package with the python3 port.  It would be even better to create the proper upstream infrastructure as well (new upstream scm and issue tracker) but that isn't 100% required by the guidelines.

Comment 3 Richard Hughes 2013-12-11 09:38:53 UTC
In Fedora 20 we ship the hawkey backend as well as the yum backend. We'll be switching to the former in Fedora 21 by default, so we don't have to worry that yum will remain python2. I've asked the other maintainers what parts of the code work with python3, but we should be fine to switch in time for F22.

Comment 4 Miro Hrončok 2013-12-11 09:52:52 UTC
Great, thanks for info

Comment 5 Jaroslav Reznik 2015-03-03 16:55:44 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:

Comment 6 Rex Dieter 2015-03-10 22:17:14 UTC
$ rpm -q PackageKit

$ rpm -qR PackageKit-hawkey PackageKit | grep python

I think we can close this?

Comment 7 Bohuslav "Slavek" Kabrda 2015-03-11 08:27:33 UTC
(I see you already closed this, so just FTR: No subpackage of PackageKit depends on Python any more. so nothing to fix here)

Note You need to log in before you can comment on or make changes to this bug.