From flud

[edit] Code Format and Conventions

Please consult the Python Style Guide for code formatting, we agree with pretty much everything listed there. All files in flud use tabs for indenting, with tabs set to 4space. Continued lines (broken at < 80 chars) should be indented at tab boundaries, i.e., don't mix tabs and spaces when indenting continued lines.

Many flud classes use doctest. Please do use doctest where possible.

As always, there is room for improvement in the codebase. If you notice formatting that is broken, feel free to fix.

[edit] Participating (submitting code)

Contributions are welcome from all, and will initially be received as patches. Developers who contribute regularly will be granted direct repository access (note, at some point, we will likely migrate from svn to hg or bazaar, at which point this whole "granting access" problem largely goes away).