There should be only one space after the ,
character.
A continuation line is indented farther than it should be for a hanging indent.
Comment indentation should be a multiple of four.
pass
statement PYL-W0107The pass
statement used here is not necessary. You can safely remove this.
A visual indented line has the same indentation as the next logical line. This can make it hard to read.
There should be only one space after the ,
character.
#
for block comment FLK-E266There should be only one leading #
for a block comment.
Closing brackets should match the same indentation level of the line that their opening bracket started on.
There should be one space before and after all operators.
It is recommended to put a newline at the end of the file.
Comments should be indented relative to the code in the block they are in.
Functions named I
, O
, and l
can be very hard to read. This is because the letter I
and the letter l
are easily confused, and the letter O
and the number 0
can be easily confused. Change the names of these functions to something more descriptive.
Multiple statements should be on their own separate lines. This improves readability.
There should be one space after keywords.
#
FLK-E262Inline comments should have one space before the pound sign #
and the comment itself.
There should be one space before and after bitwise and shift operators (<<
, >>
, &
, |
, ^
).
There should be no whitespace after the final character in a line.
There should be only one space before or after operators.
There should be only one space before a keyword.
One blank line is expected between the methods of a class.