Tabs vs. spaces caused the script to fail to run, whitespace issues and inconsistencies are just cosmetic. PEP-8 requires comments to be max 72 characters wide; bit wider is usually OK but these lines were ridiculously long.
Signed-off-by: Adam Williamson awilliam@redhat.com
To be specific on whitespace issues: this fixes trailing whitespaces, lines which contained nothing but spaces, and normalizes to one blank line between function definitions and two blank lines before a class definition.
Thank you, Adam. I did not pay much attention to the trailing whitespaces and the empty lines so far. I guess, I will have to. I know that I can make vim show me the end of lines, so I am able to tell, if there is a trailing whitespace using :set list, and I have set the replacement of tabs to produce 4 spaces instead. However, I probably was not consistent enough. I did not know, that comments should be shortened to those number of characters.
:set list
Thanks for this.
Pull-Request has been merged by lruzicka
yeah, the comment line width thing isn't something everyone sticks to, but it's generally a good idea to at least keep it under 100 chars :) these lines were actually wrapping on a 1080-wide window...
Tabs vs. spaces caused the script to fail to run, whitespace
issues and inconsistencies are just cosmetic. PEP-8 requires
comments to be max 72 characters wide; bit wider is usually OK
but these lines were ridiculously long.
Signed-off-by: Adam Williamson awilliam@redhat.com