Project

General

Profile

Code format checker

We use pylint as our code checker. Pylint plus the auto-format-on-save feature included in Eclipse will keep the code style of the project. Following there are the parameters used to configure both tools correctly.

Pylint

By default, we are not going to use any special parameter. It is supposed that Pylint (http://www.logilab.org/857) default options are ensuring the standard. Any warning issues should be treated as an error, and should be fixed before commiting the file to the subversion repository. We agree that sometimes the default options of Pylint are very strict, in such a case, a bug should be reported and after the discussion, we will relax the option or not depending on what we agree. The list of options to be passed to Pylint currently is empty.

TODO: Add a commit-hook mechanism in the subversion repository to cancel the commit if a warning is shown.

Eclipse formating

TBD