I believe that for developer, it should not matter of tox is run on Python 2 or 3, as the functionality should be the same on both Pythons. Therefore I'd like /usr/bin/tox to be Python 3 (and only version of that binary). I can prepare a patch, if you give me blessing.
I agree. If you have the cycles, please go ahead.
Will work on that. Requested ACLs.
Rawhide: http://koji.fedoraproject.org/koji/taskinfo?taskID=15214932
F25: http://koji.fedoraproject.org/koji/taskinfo?taskID=15214992
python-tox-2.3.1-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-6d48208a7f
python-tox-2.3.1-3.fc25 has been pushed to the Fedora 25 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-2016-6d48208a7f
python-tox-2.3.1-3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
The change introduces a regression: http://pkgs.fedoraproject.org/cgit/rpms/python-tox.git/commit/?h=f25&id=1fd92e9476019ba4f022b89ab900acff2d5db789 If you had /usr/bin/tox installed in F24, that binary gets removed when upgrading to f25
Well the only way to "fix" that is to obsolete python-tox from python3-tox and I'm afraid we cannot do that.
We could remove python2-tox entirely and obsolete/provide python-tox and python2-tox from python3-tox. Thoughts? Does anything actually depend on the tox module in the Python 2 world of Fedora? $ repoquery --whatrequires python-tox --alldeps python-django-federated-login-0:1.0.0-10.fc25.noarch python2-detox-0:0.10.0-2.fc25.noarch For the first one I see no reason. The socond one might be updatable to py3 as well.
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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.