Tox fails with no such option: --pre #126
Comments
Original comment by @hpk42 fix issue126: depend on virtualenv>=1.10.1 so that we can rely → <<cset 7a16cd37007c>> |
Original comment by cpcloud Upgrading my virtualenv to 1.10.1 "fixed" the problem. Not sure how many people are still using older versions. |
Original comment by @hpk42 Maybe tox just needs to depend on virtualenv>=1.10.1 given that it vendors an earlier virtualenv for python2.5? |
Original comment by @jenisys I also stumbled over this problem several times. It is related with virtualenv and its In addition, there seem to be multiple copies of "virtualenv_support" sometimes. This seems to occur when you install/upgrade virtualenv once with pip and once with easy_install (setuptools). Therefore, a feasible workaround can be to remove "virtualenv" and all its "virtualenv_support" directories from the "site-packages" directory and reinstall "virtualenv" again. Maybe the best way is that the configuration option "install_command" is not only a function of the python version but also of the pip version (that gets installed per default). WORK-AROUNDS:
|
Offending line: https://bitbucket.org/hpk42/tox/src/f7f70c5ce0b49656688bb78f8b4f5a1a8f489d7f/tox/_config.py?at=default#cl-333
This option fails with
pip==1.3.1
.The text was updated successfully, but these errors were encountered: