Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1342497 - pungi: pungi requires both Python 2 and Python 3
Summary: pungi: pungi requires both Python 2 and Python 3
Alias: None
Product: Fedora
Classification: Fedora
Component: pungi
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Dennis Gilmore
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2016-06-03 11:48 UTC by Tomas Orsava
Modified: 2016-06-06 09:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-06-06 09:37:55 UTC
Type: Bug

Attachments (Terms of Use)

Description Tomas Orsava 2016-06-03 11:48:06 UTC
The pungi RPM requires both Python 2 and Python 3.

Except in very special circumstances, there is no need for one package
to drag in both Python stacks. Usually, this is a packaging error: for
example, a stray "/usr/bin/python" shebang in a Python 3 package can
introduce a Python 2 dependency.

Please split your package, or remove the stray dependencies.
There is a section on shebangs in the Python RPM Porting Guide [0]
which covers this issue.

It's ok to do this in Rawhide only, however, it would be greatly
appreciated if you could push it to Fedora 24 as well.

If anything is unclear, or if you need any kind of assistance, you can
ask on IRC (#fedora-python on Freenode), or reply here. We'll be happy
to help investigating or fixing this issue!


Comment 1 Lubomír Sedlář 2016-06-06 06:44:34 UTC
This is fully intentional. Main codebase of Pungi is Python 2 only (mostly due to dependency on koji). However, there is a separate script that depends on pylorax, which is Python 3 only. This script is invoked at runtime as a subprocess.

See here for some more details:
It is used here:

What we could do is split this single script into a subpackage on its own, but the main package would still have to depend on it. Is that desirable? What advantages would it have?

Comment 2 Tomas Orsava 2016-06-06 09:37:55 UTC
Hi Lubomir!

Invoking it as a subprocess is fine, I apologize for a misfiled bug. In the vast majority of cases needing both Python stacks is a mistake, but in this case it does make sense.

That is not to say it wouldn't be better to have it all run entirely on Python 3, as Python 2 will be end-of-life quite soon and Fedora 25 will be distancing itself away from it as possible. Hopefully, upstream finds the time to port it in the future.

Thank you for the feedback!

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