Changes

Jump to: navigation, search

Programming guidelines

348 bytes added, 19:57, 2 February 2009
no edit summary
pass
</code>
* Run <code>pylint</code> on your code before checking in, and use the output to reasonably clean up the code. Note that you must run <code>pylint</code> in the <code>src</code> directory.If import errors still occur, add a PYTHONPATH. Example usage: [email protected]:~/programs/trunk/src$ PYTHONPATH=plugins/lib/ pylint --include-ids=y --reports=y plugins/mapservices/googlemap.pySet reports to n to have less output. Try to obtain a score of minimum 9/10. Info on the codes can be found here: [http://www.logilab.org/card/pylintfeatures]
* Always develop with [http://www.gramps-project.org/wiki/index.php?title=Coding_for_translation language translation] in mind
* Reduce dependencies (imports) between files.

Navigation menu