RVMI
static code analysis with 'pylint'
What about doing static code analysis with pylint or something similar?
It seems to catch a lot of errors that can easily be found with static code analysis and could prevent annoying crashes at runtime.
It would also be possible to easily integrate it with travis_ci so one wouldn't need to check manually.
Going through old issues that has not been addressed.
Linting in general I think is a good idea. At the moment, I think we would be drown in noise over more important issues.
In the short term, I think adding type annotation and type traceability will prevent the most common misstakes in combination with better validation logic.
There has been some work on static code analysis with EzSkiROS, this could be run as a linter - but that is larger undertaking.
If anyone wants to contribute a good pylint configuration I would be happy to merge it.
