Coding style
Bug #226661 reported by
Adam Rooke
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PyRoom |
Fix Released
|
Medium
|
Unassigned |
Bug Description
First off, sorry for not contributing anything for the last few months but have been pretty busy. On study leave now though, so that leaves me lots of time :-) Nice to see that pyroom has still be progressing.
I think it would be a could idea if we modified the code so that it follows some of the standards suggested here: http://
Any thoughts?
Related branches
Changed in pyroom: | |
assignee: | nobody → caio-alonso |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in pyroom: | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
Why not starting a PEP-008 branch out of trunk, and merge it when the PEP it's fine?
This script might help checking source code:
http:// trac.browsersho ts.org/ browser/ trunk/devtools/ pep8/pep8. py?format= txt
Pylint helps a lot, too:
$ sudo apt-get install pylint