Project

General

Profile

Defect #16

Review code and organize/change to match Python coding guidelines

Added by Deoren Moor almost 7 years ago.

Status:
Assigned
Priority:
Normal
Assignee:
Category:
Code cleanup
Target version:
-
Start date:
12/05/2010
Due date:
% Done:

0%

Estimated time:
Affected Version:
Resolution:

Description

I'm guilty of not following these due to old habits with C, Perl, etc.

http://bayes.colorado.edu/PythonGuidelines.html
http://www.python.org/dev/peps/pep-0008/
http://python.net/~goodger/projects/pycon/2007/idiomatic/handout.html

Not all of those may apply (non python.org links), but look to be useful.

Associated revisions

Revision 16 (diff)
Added by Deoren Moor almost 7 years ago

[issue #16]
Beginning of code cleanup: One import per line, docstring below shebang, authorship info moved.

Revision 17 (diff)
Added by Deoren Moor almost 7 years ago

[issue #16]
Code cleanup: Looks like I placed the authorship info in the wrong place. Fixed (according to http://bayes.colorado.edu/PythonGuidelines.html ).

Revision 19 (diff)
Added by Deoren Moor almost 7 years ago

[issue #16]
Wrapped code in a main() block and moved OptionParser import to where other modules are imported.

Revision 23 (diff)
Added by Deoren Moor almost 7 years ago

[issue #16]
Added missing docstring to WriteFile function and split part of the print statement onto the next line. Still many more throughout code that exceed 80 chars.

Revision 87 (diff)
Added by Deoren Moor almost 7 years ago

[issues #16]
Updated build.py to follow PEP 8 coding conventions.

Also available in: Atom PDF