Red Hat Bugzilla – Bug 1010767
Last modified: 2015-11-20 02:53:50 EST
Its latest version is 1.6.1, and from pypi index I can see it supports py3.
From changelog I alos can see that you've disable py3k support.
Now we have a package which may use it for tests, can you update it with py3k enabled?
now that with python 3.3.0 virtualenv is part of the core and we have a pyvenv/pyvenv-3.4 command. Is the dep on #537246 still needed? From a quick
glance it seems that BZ could be closed now.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
There is already tox 2.1.1, are you going to release the update? I need it especially for el6.
Michel, I'm not sure, I really understand you. You want python3-tox in EL6?
It seems I can proceed here.
no, python-tox of course. But newer version. that it is there. I had some problem with the 1.4.x and upgrade helped. But installing it by pip isn't convenient. I perceive installing by pip to system path stupid (can easily collide with RPMs) and when I install it to home by --user switch, I don't have tox on $PATH
- please don't capture other bugs and write your requests there. This bug is about adding a python3 subpackage to tox. It is NOT(!) about upgrading to a later version in EPEL. For each request, please open a new report. It's better to differentiate then.
- About upgrades in epel: https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies
This is something we can do, but we need to evaluate, if we don't break someone else.
Sorry for that, I just created a dedicated bug: https://bugzilla.redhat.com/show_bug.cgi?id=1241966
I see that python3-tox is now in Fedora. Can this bug can be closed, or is there more to do?
Thank you Petr! This somehow dropped from my screen.