Use Pylint instead of pep8 in travis ci
pep8 just checks style conventions whereas pylint also checks for compile issues which is useful before running actual tests.
just read about pylint. Seems like a good idea to have it.
let other @CCI-MOC/bmi-breakers also respond
+1
+1000 - I just looked at the documentation. Seems it has lot of stuff like code analysis(which can help in refactoring etc).
It would be a good idea to enable one feature of pylint at a time, like how we are doing it in HIL.
https://github.com/CCI-MOC/hil/blob/master/ci/pylint_tests.sh#L8-L17
I think it took 4-5 PRs to enable those checks in pylint.
Looks like we'll be rewriting most of the code, so it would be a good idea to enable pylint from the beginning.