Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1024796 - (PY3PACKAGER) fedora-packager: Use Python 3 instead of Python 2 [NEEDINFO]
fedora-packager: Use Python 3 instead of Python 2
Status: NEW
Product: Fedora
Classification: Fedora
Component: fedora-packager (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Dennis Gilmore
Fedora Extras Quality Assurance
: FutureFeature, Reopened
Depends On: 1014549 1024795 1024805 1024809 1024816 1024827 1024845
  Show dependency treegraph
Reported: 2013-10-30 09:02 EDT by Miro Hrončok
Modified: 2018-11-14 11:43 EST (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 06:31:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
mhroncok: needinfo? (dennis)
mhroncok: needinfo? (nonamedotc)

Attachments (Terms of Use)

  None (edit)
Description Miro Hrončok 2013-10-30 09:02:13 EDT
Hi, we would like to use Python 3 on the default installation instead of Python 2 on Fedora 22.


While this package is not in minimal buildroot, it belongs to fedora-packager stack. We would like to switch to Python 3 there as well.

The goal here is, that for F22 you should use Python 3 instead of Python 2 in this package.

Please, help us update to Python 3 flawlessly.

Check if upstream already support Python 3, if yes, use it and add the 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, say so and we can solve the problem together.

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

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 Jaroslav Reznik 2015-03-03 10:10:15 EST
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 2 Nils Philippsen 2015-08-14 11:09:26 EDT
Zbigniew, I don't understand why this bug should depend on whether 2to3, pynche, msgfmt.py, pygettext.py, smtpd.py come from python-tools or python3-tools. Care to explain?
Comment 3 Zbigniew Jędrzejewski-Szmek 2015-08-14 11:55:21 EDT
Yeah, wrong bug.
Comment 4 Ville Skyttä 2015-11-21 14:44:11 EST
Comment 5 Christian Stadelmann 2016-04-23 07:46:56 EDT
Ville Skyttä: The link you posted is broken. 

Dennis Gilmore / maintainer: Is there any progress on this? Are you interested in pull requests?

I'd like to see fedora-client to be ported to python3 for making fedora-easy-karma work (see bug #1329629)
Comment 6 Ville Skyttä 2016-04-23 08:26:30 EDT
(In reply to Christian Stadelmann from comment #5)
> Ville Skyttä: The link you posted is broken.

I suppose a pagure update or something has broken it. Anyway, that PR has been merged, https://pagure.io/fedora-packager/3a597f82f0e8e464f859458e4230f2e1e7730517
Comment 7 Till Maas 2016-05-22 10:30:58 EDT
AFAICS the next step for the fedora_cert part would be to create python2-fedora-cert and python3-fedora_cert subpackages that provides the modules for each python version and then make the fedora-cert tool use python3 for F24+. For F23- and EPEL the tool needs to use python or should at least depend on the python2 subpackage to not break dependencies of other tools, since there is no separate module subpackage atm.
Comment 8 Fedora End Of Life 2016-07-19 06:31:38 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 9 Jan Kurik 2016-07-26 00:12:24 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
Comment 10 Fedora End Of Life 2017-11-16 13:34:44 EST
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 11 Zbigniew Jędrzejewski-Szmek 2017-11-16 15:07:14 EST
fedora-packager- still uses python2.
Comment 12 Miro Hrončok 2018-07-31 12:57:42 EDT
What's the status of this one?
Comment 13 Miro Hrončok 2018-11-07 12:19:22 EST
Anything the Python Main team can do to move this forward?
Comment 14 Miro Hrončok 2018-11-14 11:43:59 EST
Anyone? Any response?

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