Personally, I am really reluctant to have pylint checks run automatically by travis. My experience with pylint is that is quite good at catching things, but often makes mistakes, or fails to understand things. This will cause builds to fail on what may well be unimportant errors, or even warnings (unless we use `pylint -E`), unless we start littering the code with pylint overrides. 

NB, pytest can run pep8 tests, using the pep8 plugin, and then integrate the results into the normal pytest report - might be worth having a look at this.