Menu
▾
▴
General development guidelines
General development guidelines
This page should contain recommendations for efficient coding. We will try to keep our coding standards as high as possible.
General
- Commit often, even after very small bug fixes.
- Always add a message when committing through svn. Use the -m "Your message goes here" option and describe what is new in the code.
Python
- Use 4 space indenting instead of tabs. Provides better readability.
- Use [pylint] on all scripts uploaded on the SVN. Try to fix as many possible issues, but do not force the perfect 10.
- Don't use other comments, excepting the doc strings. A good code should be self-explaining. If something is not clear in a sequence written by somebody else, post a request for changes in the tickets section.
