Python linter checks in the GitHub Travis CI build
Posted: Fri Mar 09, 2018 6:39 pm
We are adding a stage of python code style checking into our GitHub Travis CI build process; PR's should not be merged if they are failing this stage. If a PR of yours fails this stage, please review the associated report (found via the respective "Details" link in the CI section of your PR page), make the required changes and check locally, then update your PR.
There are a variety of ways to check for such things locally; in general we recommend doing your python coding with PyCharm, which supports such checking in a few ways.
If you have questions about this general process, or about particular error reporting you get from this, feel free to post those questions here. Once resolved I may curate (edit or delete) any such posts here in order to keep this thread concise/clean.
(Related to the above, I invite comment on this initial message, I'll then edit and curate the thread).
There are a variety of ways to check for such things locally; in general we recommend doing your python coding with PyCharm, which supports such checking in a few ways.
If you have questions about this general process, or about particular error reporting you get from this, feel free to post those questions here. Once resolved I may curate (edit or delete) any such posts here in order to keep this thread concise/clean.
(Related to the above, I invite comment on this initial message, I'll then edit and curate the thread).