New issue 280: Having interpreters that aren't installed in envlist causes tox to refuse to run https://bitbucket.org/hpk42/tox/issues/280/having-interpreters-that-arent-installed
ceridwenv: I have a tox.ini that looks like this. ``` [tox] # envlist = py27, py33, py34, py35, pypy, jython, pylint envlist = py27, py33, py34 skip_missing_interpreters = true [testenv] deps = py27,pypy,jython: funcsigs lazy-object-proxy py27,py33,pypy,jython: singledispatch six wrapt pylint: hg+https://bitbucket.org/logilab/pylint commands = python -m unittest discover -s {envsitepackagesdir}/astroid/tests -p "unittest*.py" ``` As I understand it, this should run with any missing interpreters skipped. Instead, running `tox` with CPython 2.7 and 3.4 installed, but not 3.3, gives: ``` ERROR: InterpreterNotFound: python3.3 ERROR: unknown environment 'py27' ``` Different combinations of missing interpreters can give different InterpreterNotFound and unknown environment errors, and it's not deterministic which will be reported. Commenting out the `commands = ` line causes it to run with: ``` py27: commands succeeded SKIPPED: py33: InterpreterNotFound: python3.3 py34: commands succeeded congratulations :) ``` As I'd expect, but of course this then doesn't run the tests. `tox -e` using py27 or py34 will run, `tox -e py33` gives the same error as `tox`. This is on Ubuntu Linux. I've tried both version 1.8.0, the version packaged by Ubuntu, and version 2.1.1 installed with pip, and they exhibit the same behavior. _______________________________________________ pytest-commit mailing list pytest-commit@python.org https://mail.python.org/mailman/listinfo/pytest-commit
