Upstream, this software supports Python 3. Please provide a Python 3 package for Fedora. According to the Python packaging guidelines [0], software must be packaged for Python 3 if upstream supports it. The guidelines give detailed information on how to do this, and even provide an example spec file [1]. Since users aren't expected to import this tool from Python code, you can just switch to /usr/bin/python3. Alternatively, if you want or need to keep a Python 2 version, the current best practice is to provide subpackages -- this is called "Common SRPM" in the guidelines. It's OK to do this in Rawhide only, however, it would be greatly appreciated if you could push it to Fedora 25 as well. If you need more instructions, a guide for porting Python-based RPMs is available at [2]. If anything is unclear, or if you need any kind of assistance with the porting, you can ask on IRC (#fedora-python on Freenode), or reply here. We'll be happy to help! [0] https://fedoraproject.org/wiki/Packaging:Python [1] https://fedoraproject.org/wiki/Packaging:Python#Example_common_spec_file [2] http://python-rpm-porting.readthedocs.io/
Hmmm. Well we are upstream :-) and I am not sure if we fully support Python 3 yet. We might have put that classifier into setup.py a bit prematurely. Our tests are not covering Python 3 at all right now. And our target deployment platform for waiverdb in Fedora infra is (for now) Python 2 on EPEL7. Also waiverdb is an application, not a Python library, so I don't think there is any reason to ship both Python 2 and Python 3 versions at the same time. What we probably want to do is built it against Python 2 in EPEL7 and against Python 3 in Fedora -- after we ensure we are testing both of those configurations in our CI.
Thanks for your response, Dan. I must have got a wrong understanding that Python 3 is supported from the first look at the repository. You may close the issue, or keep it open until Python 3 is fully supported.
Oh yeah I thought we must have put in the "Programming Language :: Python :: 3" classifier, which I guess is the usual way of signifying proper Python 3 support. But it looks like we have *no* Trove classifiers declared at all. :-) I will leave this open as an RFE because we certainly do want first-class Python 3 support, and waiverdb is a small and new project so it will be easy to achieve. We just need to make sure it's regularly tested.
Any chance to move this forward? This is likely to be widely installed now because of https://pagure.io/fesco/issue/1810.
FYI upstream issue is: https://pagure.io/waiverdb/issue/91 I am planning to try and switch to Python 3 for Fedora while keeping Python 2 compatibility for EPEL7.
waiverdb-0.9.1-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-1ac1cb847d
waiverdb-0.9.1-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-9b51a1d05f
waiverdb-0.9.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-a33f1a19be
waiverdb-0.9.1-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-9b51a1d05f
waiverdb-0.9.1-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-a33f1a19be
waiverdb-0.11.0-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-535b7a96a5
waiverdb-0.11.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-eade1b9803
waiverdb-0.11.0-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-29e2ddd9d4
waiverdb-0.11.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-eade1b9803
waiverdb-0.11.0-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-29e2ddd9d4
waiverdb-0.11.0-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-535b7a96a5
waiverdb-0.11.0-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
waiverdb-0.11.0-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
waiverdb-0.11.0-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.