Description of problem: When packaging Python projects with bdist_rpm from python34-setuptools it creates a spec file that tries to invoke "python3 setup.py build". Since today none of its dependencies provides python3. Presumably also any entry points will point to python3 in their hashbangs rendering them unable to start or locate libraries installed for python3.4. Version-Release number of selected component (if applicable): python34-setuptools-39.2.0-3.el7.noarch How reproducible: Always Steps to Reproduce: 1. Install python34-setuptools and keep python36 from being installed. 2. Run python3.4 setup.py bdist_rpm in some Python 3 project. Actual results: [...] + python3 setup.py build /var/tmp/rpm-tmp.7F0CJk: line 29: python3: command not found error: Bad exit status from /var/tmp/rpm-tmp.7F0CJk (%build) Expected results: Successful completion resulting in packaged Python software. Additional info: As i noted above this probably extends to scripts installed for entry points as well, if this issue is addressed, please look in to that question too.
A very dirty fix would be to patch bdist_rpm to use python3.X in the spec file instead of python3.
AFAIK the responsible code is part of distutils (standard library).
Patching bdist_rpm seems like a good start but please see my note about entry points too!
console scripts entrypoints are created with the caller script. e.g. if you call python3.4 setup.py install, the entrypoints will have /usr/bin/pythno3.4 shebangs.
I won't have time to work on this. Feel free to take it.
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.