Tox is used as a tool for creating and managing virtualenv environments
-and running tests in them. As of tox-1.4 there are some issues frequen
+and running tests in them. As of tox-1.4 there are some issues frequently
coming up with its configuration language:
- there is no way to instruct tox to parametrize testenv specifications
versions, against python2.6, 2.7 interpreters and on ``linux`` and
``win32`` platforms. Today you would have to
write down 2*2*2 = 8 ``[testenv*]`` sections and then instruct
on the respective platform with a respective environment name list.
+tox to .
With tox-1.X there will be no need to write down such boilerplate stuff.
Without further ado, here is how a ``tox.ini`` would look like::
Let's look at the next config item, the declaration of the generic
-testenv. All the eight testenvironments will derive from this one.
+testenv. All the eight testenvironments will derive from this one.
Unlike with earlier tox versions, there is no need to write down
eight different ``[testenv:...]`` sections::
These two conditional settings will lead to either ``windows`` or
``linux`` as the platform string. When the test environment is run,
-its platform string needs to be contained
match the string returned
+its platform string needs to be contained the string returned
from ``platform.platform()``. Otherwise the environment will be skipped.
The next configuration item in the ``testenv`` section deals with
the two executable s, depending on if ``py26`` or ``py27``
+This defines executable, depending on if ``py26`` or ``py27``
appears in the environment name.
The last config item is simply the invocation of the test runner::