The texlive-pythontex RPM requires both Python 2 and Python 3:
$ dnf repoquery --repo=rawhide --requires texlive-pythontex | grep python
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 
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 28 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!
I think this might be one of the "very special circumstances".
pythontex is already split out into python2 and python3 versions, with the main script doing python version detection and launching the appropriate version:
if sys.version_info == 2:
import depythontex2 as depythontex
elif sys.version_info == 3:
import depythontex3 as depythontex
Now, I _could_ split out the python3 files into their own subpackage, but upstream assumes they will both be present, so the net result will be the same.
Let me know how you want me to handle this.
Thanks for the explanation.
If that is how upstream intends it, then please keep the package as it is, we will whitelist it in our sanity checks.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.
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 29 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.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.
Still an issue -- in the long run, Python 2 support will need dropping. However, it's tracked in Bug #1738161.