Configure Tox and Use It to Drive Travis #1173
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Uses parallel testing where it's able to * Sets PYTHONHASHSEED=0 Where it's required
Using tox to drive the tests instead of travis itself means that we only need to configure how to run tests in one location. We use tox for that location because tox can run on developer machines as well as on travis so it has the best reusability.
A trailing slash in a directory name is essentially a noop unless the directory name itself contains a trailing slash.
We need the docs directory for ``python setup.py``
|
merge 👍 |
dstufft
added a commit
that referenced
this pull request
Aug 28, 2013
Configure Tox and Use It to Drive Travis
lock
bot
added
the
auto-locked
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
.travis.ymlso it dispatches the testing logic to ToxEssentially I got tired of remembering that I needed to run
py.testinstead ofpy.test -n 8on Python 3.2 and that I needed to runPYTHONHASHSEED=0 py.test -n 8on Python 3.3. This makes it so the command is alwaystox -e pyNN. Additionally it consolidates the testing configuration in one place (tox.ini) so that we only need to maintain one configuration. Finally we make sure that our documentation always builds because we want good documentation.