Development Team/Code guidelines: Difference between revisions
| Line 55: | Line 55: | ||
When possible use tools to check your code, this will save lots of time for everybody involved. | When possible use tools to check your code, this will save lots of time for everybody involved. | ||
Please try to use [http://www.logilab.org/857 pylint] to verify your patch for things like exceeding 80 columns etc., unused imports and unused variables. Pylint is not a tool you can rely on 100%, but it helps to follow some guidelines and to avoid the most stupid errors like typos. | Please try to use [http://www.logilab.org/857 pylint] to verify your patch for things like exceeding 80 columns etc., unused imports and unused variables. Pylint is not a tool you can rely on 100%, but it helps to follow some guidelines and to avoid the most stupid errors like typos. To run it: "./sugar-jhbuild run pylint sugar jarabe". | ||
[http://github.com/cburroughs/pep8.py pep8.py] catches more style errors than pylint, so make sure to run that one, too. | [http://github.com/cburroughs/pep8.py pep8.py] catches more style errors than pylint, so make sure to run that one, too. | ||