Hi,
Barry Warsaw wrote:
I can think of a couple of things you could do instead.
* Run `python2 /usr/bin/tox -e docs`
* Add a `basepython=python2` to the [docs] section of your tox.ini
Would either one of those work? I'd really like to leave /usr/bin/tox as a
Python 3 script by default, a
I can think of a couple of things you could do instead.
* Run `python2 /usr/bin/tox -e docs`
* Add a `basepython=python2` to the [docs] section of your tox.ini
Would either one of those work? I'd really like to leave /usr/bin/tox as a
Python 3 script by default, and I'd like to not ship a /us
Source: tox
Severity: important
Hello,
except for the rather surprising usage of Py3k-only for tox (which is not
mentioned in the package description) while still using the python- format, that
can cause problems when installing packages with are not py3k-ready; real world
example is OpenStack Nov
3 matches
Mail list logo