[Pytest-commit] Issue #111: tox cannot be started on itself with twice the same environment ( tox -e py27, py27) (hpk42/tox)

New issue 111: tox cannot be started on itself with twice the same environment ( tox -e py27,py27) https://bitbucket.org/hpk42/tox/issue/111/tox-cannot-be-started-on-itself-with-twice Anthon van der Neut: I am not sure it should run the same environment twice, but it should not throw an error

[Pytest-commit] Issue #113: running 'tox -- -k test_setup_py' on tox should not overwrite tox' own tox.ini (hpk42/tox)

New issue 113: running 'tox -- -k test_setup_py' on tox should not overwrite tox' own tox.ini https://bitbucket.org/hpk42/tox/issue/113/running-tox-k-test_setup_py-on-tox-should Anthon van der Neut: While adding some tests in test_z_cmdline, all with the substring 'test_

[Pytest-commit] Issue #249: tox --help and other options not depending on tox.ini should always work (hpk42/tox)

New issue 249: tox --help and other options not depending on tox.ini should always work https://bitbucket.org/hpk42/tox/issue/249/tox-help-and-other-options-not-depending Anthon van der Neut: If you don't have a `tox.ini` in your current directory, you can run `tox --version`, but when y

[Pytest-commit] Issue #250: tox colors the output of py.test if term=dumb on windows (hpk42/tox)

New issue 250: tox colors the output of py.test if term=dumb on windows https://bitbucket.org/hpk42/tox/issue/250/tox-colors-the-output-of-pytest-if-term Anthon van der Neut: If the output of `py.test` is unreadable because of the color scheme on windows, you can use `set term=dumb` to suppress

[Pytest-commit] Issue #251: detox gives command succeeded even if there was no setup.py (hpk42/tox)

New issue 251: detox gives command succeeded even if there was no setup.py https://bitbucket.org/hpk42/tox/issue/251/detox-gives-command-succeeded-even-if Anthon van der Neut: If you have a directory with **only** a `tox.ini`: ``` [tox] envlist = py27,py26,py34,py33,pypy [testenv] deps=pytest