Closed pytoxbot closed 8 years ago
Original comment by @fasaxc
I just hit this and worked around by putting this in my [testenv]
section of tox.ini
:
install_command =
pip install -U {opts} {packages}
Original comment by @campbellr
Excellent, thanks!
Original comment by @kmike
I'm using this workaround: https://github.com/tpeng/python-crfsuite/blob/master/tox.ini
Original comment by @campbellr
I'm seeing what looks to be the exact same problem here.
@kmike did you ever figure out a workaround for this?
@kmike sorry for bothering after such a long time, but is this still a thing, or can we close this?
@obestwalter I just tried it, and python-crfsuite tox tests seem to work without a workaround on my machine.
Hi,
Tox doesn't install the package being tested for me, seemingly because it thinks it is already installed.
The workaround is to add
python setup.py install
to commands, but this is suboptimal (dependencies can be processed twice, wheels are not installed, and this is not how tox used to work).I'm using tox 1.7.1, virtualenv 1.11.6, pip 1.5.6 and setuptools 4.0.1. The OS is Mac OS X 10.9.3; the issue is reproducable with both Python 2.7.5 and python 3.4.1 virtualenvs (Pythons are installed using homebrew).
I tried to downgrade to virtualenv 1.11.2 and run tox -r -e py27, but it didn't help. Downgrading to tox 1.6.1 also didn't help.
After running tox own tests,
.tox/py27/log/py27-2.log
looks suspicious:The suspicious line is
-- sdist is not installed because pip finds the same package in a local folder; this happen even when a new environment is created, so the package doesn't get installed into test virtuelanv at all.
and the tests fail: