| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(exception) issues
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This behavior is prefered to enclosing the string with parenthesis.
When using "\" remember to close the strings with quotation marks to
have a clean output.
Prefered:
message = "long string " \
"end of long string"
Not prefered:
message = ("long string "
"end of long string"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When deviding a string into two lines one must use pythons automatic
string concatenation (python concatenates strings that are in different
line but are inside parenthesis). Do not use the "\" in the string as
this will cause strange and unwanted output.
Yes:
print("long string"
"rest of string")
No:
print("long string \
rest of string")
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Indendtation should be 4 spaces. There was a function indented with
8 spaces.
- Lines should be shorted than 80 chars. It just looks pretty :)
Think of terminals whith only 80 char of length. Think of debuging
in rescue mode.
- Change also the print statements. Just getting ready for python 3000.
- Get some spaces between elifs
- There should not be any lines ending in spaces.
- This can all be read in the python code conventions
http://www.python.org/dev/peps/pep-0008/
|
|
|
|
|
| |
The new variable name better expresses the objective of the issue state.
This will help avoid confusion for the plugin developer.
|
|
|
|
| |
reporting that much
|
| |
|
|
|
|
| |
class (so everybody can use something simple to report state)
|
| |
|
|
|