tlsfuzzer/tlslite-ng

View on GitHub
tlslite/mathtls.py

Summary

Maintainability
F
3 days
Test Coverage
B
84%

File mathtls.py has 834 lines of code (exceeds 250 allowed). Consider refactoring.
Open

# Authors: 
#   Trevor Perrin
#   Dave Baggett (Arcode Corporation) - MD5 support for MAC_SSL
#   Yngve Pettersen (ported by Paul Sokolovsky) - TLS 1.2
#   Hubert Kario - SHA384 PRF
Severity: Major
Found in tlslite/mathtls.py - About 2 days to fix

    Function calc_key has a Cognitive Complexity of 25 (exceeds 5 allowed). Consider refactoring.
    Open

    def calc_key(version, secret, cipher_suite, label, handshake_hashes=None,
                client_random=None, server_random=None, output_length=None):
        """
        Method for calculating different keys depending on input.
        It can be used to calculate finished value, master secret,
    Severity: Minor
    Found in tlslite/mathtls.py - About 3 hrs to fix

    Cognitive Complexity

    Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

    A method's cognitive complexity is based on a few simple rules:

    • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
    • Code is considered more complex for each "break in the linear flow of the code"
    • Code is considered more complex when "flow breaking structures are nested"

    Further reading

    Cyclomatic complexity is too high in function calc_key. (18)
    Open

    def calc_key(version, secret, cipher_suite, label, handshake_hashes=None,
                client_random=None, server_random=None, output_length=None):
        """
        Method for calculating different keys depending on input.
        It can be used to calculate finished value, master secret,
    Severity: Minor
    Found in tlslite/mathtls.py by radon

    Cyclomatic Complexity

    Cyclomatic Complexity corresponds to the number of decisions a block of code contains plus 1. This number (also called McCabe number) is equal to the number of linearly independent paths through the code. This number can be used as a guide when testing conditional logic in blocks.

    Radon analyzes the AST tree of a Python program to compute Cyclomatic Complexity. Statements have the following effects on Cyclomatic Complexity:

    Construct Effect on CC Reasoning
    if +1 An if statement is a single decision.
    elif +1 The elif statement adds another decision.
    else +0 The else statement does not cause a new decision. The decision is at the if.
    for +1 There is a decision at the start of the loop.
    while +1 There is a decision at the while statement.
    except +1 Each except branch adds a new conditional path of execution.
    finally +0 The finally block is unconditionally executed.
    with +1 The with statement roughly corresponds to a try/except block (see PEP 343 for details).
    assert +1 The assert statement internally roughly equals a conditional statement.
    Comprehension +1 A list/set/dict comprehension of generator expression is equivalent to a for loop.
    Boolean Operator +1 Every boolean operator (and, or) adds a decision point.

    Source: http://radon.readthedocs.org/en/latest/intro.html

    Cyclomatic complexity is too high in function paramStrength. (12)
    Open

    def paramStrength(param):
        """
        Return level of security for DH, DSA and RSA parameters.
    
        Provide the approximate level of security for algorithms based on finite
    Severity: Minor
    Found in tlslite/mathtls.py by radon

    Cyclomatic Complexity

    Cyclomatic Complexity corresponds to the number of decisions a block of code contains plus 1. This number (also called McCabe number) is equal to the number of linearly independent paths through the code. This number can be used as a guide when testing conditional logic in blocks.

    Radon analyzes the AST tree of a Python program to compute Cyclomatic Complexity. Statements have the following effects on Cyclomatic Complexity:

    Construct Effect on CC Reasoning
    if +1 An if statement is a single decision.
    elif +1 The elif statement adds another decision.
    else +0 The else statement does not cause a new decision. The decision is at the if.
    for +1 There is a decision at the start of the loop.
    while +1 There is a decision at the while statement.
    except +1 Each except branch adds a new conditional path of execution.
    finally +0 The finally block is unconditionally executed.
    with +1 The with statement roughly corresponds to a try/except block (see PEP 343 for details).
    assert +1 The assert statement internally roughly equals a conditional statement.
    Comprehension +1 A list/set/dict comprehension of generator expression is equivalent to a for loop.
    Boolean Operator +1 Every boolean operator (and, or) adds a decision point.

    Source: http://radon.readthedocs.org/en/latest/intro.html

    Function calcFinished has a Cognitive Complexity of 15 (exceeds 5 allowed). Consider refactoring.
    Open

    def calcFinished(version, masterSecret, cipherSuite, handshakeHashes,
                     isClient):
        """Calculate the Handshake protocol Finished value
    
        :param version: TLS protocol version tuple
    Severity: Minor
    Found in tlslite/mathtls.py - About 1 hr to fix

    Cognitive Complexity

    Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

    A method's cognitive complexity is based on a few simple rules:

    • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
    • Code is considered more complex for each "break in the linear flow of the code"
    • Code is considered more complex when "flow breaking structures are nested"

    Further reading

    Function paramStrength has a Cognitive Complexity of 12 (exceeds 5 allowed). Consider refactoring.
    Open

    def paramStrength(param):
        """
        Return level of security for DH, DSA and RSA parameters.
    
        Provide the approximate level of security for algorithms based on finite
    Severity: Minor
    Found in tlslite/mathtls.py - About 1 hr to fix

    Cognitive Complexity

    Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

    A method's cognitive complexity is based on a few simple rules:

    • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
    • Code is considered more complex for each "break in the linear flow of the code"
    • Code is considered more complex when "flow breaking structures are nested"

    Further reading

    Function calc_key has 8 arguments (exceeds 4 allowed). Consider refactoring.
    Open

    def calc_key(version, secret, cipher_suite, label, handshake_hashes=None,
    Severity: Major
    Found in tlslite/mathtls.py - About 1 hr to fix

      Function calcFinished has 5 arguments (exceeds 4 allowed). Consider refactoring.
      Open

      def calcFinished(version, masterSecret, cipherSuite, handshakeHashes,
      Severity: Minor
      Found in tlslite/mathtls.py - About 35 mins to fix

        Function calcMasterSecret has 5 arguments (exceeds 4 allowed). Consider refactoring.
        Open

        def calcMasterSecret(version, cipherSuite, premasterSecret, clientRandom,
        Severity: Minor
        Found in tlslite/mathtls.py - About 35 mins to fix

          Function calcMasterSecret has a Cognitive Complexity of 7 (exceeds 5 allowed). Consider refactoring.
          Open

          def calcMasterSecret(version, cipherSuite, premasterSecret, clientRandom,
                               serverRandom):
              """Derive Master Secret from premaster secret and random values"""
              if version == (3,0):
                  masterSecret = PRF_SSL(premasterSecret,
          Severity: Minor
          Found in tlslite/mathtls.py - About 35 mins to fix

          Cognitive Complexity

          Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

          A method's cognitive complexity is based on a few simple rules:

          • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
          • Code is considered more complex for each "break in the linear flow of the code"
          • Code is considered more complex when "flow breaking structures are nested"

          Further reading

          Avoid too many return statements within this function.
          Open

                  return 88  # rounded RFC 3526
          Severity: Major
          Found in tlslite/mathtls.py - About 30 mins to fix

            Avoid too many return statements within this function.
            Open

                    return 80  # NIST SP 800-57
            Severity: Major
            Found in tlslite/mathtls.py - About 30 mins to fix

              Avoid too many return statements within this function.
              Open

                      return 128  # NIST SP 800-57
              Severity: Major
              Found in tlslite/mathtls.py - About 30 mins to fix

                Avoid too many return statements within this function.
                Open

                        return 256  # NIST SP 800-57
                Severity: Major
                Found in tlslite/mathtls.py - About 30 mins to fix

                  Avoid too many return statements within this function.
                  Open

                          return 192  # NIST SP 800-57
                  Severity: Major
                  Found in tlslite/mathtls.py - About 30 mins to fix

                    Avoid too many return statements within this function.
                    Open

                            return 152  # rounded RFC 3526
                    Severity: Major
                    Found in tlslite/mathtls.py - About 30 mins to fix

                      Avoid too many return statements within this function.
                      Open

                              return 168  # rounded RFC 3526
                      Severity: Major
                      Found in tlslite/mathtls.py - About 30 mins to fix

                        Avoid too many return statements within this function.
                        Open

                                return 112  # NIST SP 800-57
                        Severity: Major
                        Found in tlslite/mathtls.py - About 30 mins to fix

                          Function PRF_SSL has a Cognitive Complexity of 6 (exceeds 5 allowed). Consider refactoring.
                          Open

                          def PRF_SSL(secret, seed, length):
                              bytes = bytearray(length)
                              index = 0
                              for x in range(26):
                                  A = bytearray([ord('A')+x] * (x+1)) # 'A', 'BB', 'CCC', etc..
                          Severity: Minor
                          Found in tlslite/mathtls.py - About 25 mins to fix

                          Cognitive Complexity

                          Cognitive Complexity is a measure of how difficult a unit of code is to intuitively understand. Unlike Cyclomatic Complexity, which determines how difficult your code will be to test, Cognitive Complexity tells you how difficult your code will be to read and comprehend.

                          A method's cognitive complexity is based on a few simple rules:

                          • Code is not considered more complex when it uses shorthand that the language provides for collapsing multiple statements into one
                          • Code is considered more complex for each "break in the linear flow of the code"
                          • Code is considered more complex when "flow breaking structures are nested"

                          Further reading

                          Similar blocks of code found in 2 locations. Consider refactoring.
                          Open

                                      if label in [b"extended master secret", b"server finished",
                                              b"client finished"]:
                                          seed = handshake_hashes.digest('sha384')
                                      else:
                                          assert label in [b"key expansion", b"master secret"]
                          Severity: Minor
                          Found in tlslite/mathtls.py and 1 other location - About 45 mins to fix
                          tlslite/mathtls.py on lines 894..898

                          Duplicated Code

                          Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

                          Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

                          When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

                          Tuning

                          This issue has a mass of 38.

                          We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

                          The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

                          If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

                          See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

                          Refactorings

                          Further Reading

                          Similar blocks of code found in 2 locations. Consider refactoring.
                          Open

                                      if label in [b"extended master secret", b"server finished",
                                              b"client finished"]:
                                          seed = handshake_hashes.digest('sha256')
                                      else:
                                          assert label in [b"key expansion", b"master secret"]
                          Severity: Minor
                          Found in tlslite/mathtls.py and 1 other location - About 45 mins to fix
                          tlslite/mathtls.py on lines 886..890

                          Duplicated Code

                          Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

                          Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

                          When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

                          Tuning

                          This issue has a mass of 38.

                          We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

                          The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

                          If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

                          See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

                          Refactorings

                          Further Reading

                          Whitespace after '['
                          Open

                              S1 = secret[ : int(math.ceil(len(secret)/2.0))]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Avoid extraneous whitespace.

                          Avoid extraneous whitespace in these situations:
                          - Immediately inside parentheses, brackets or braces.
                          - Immediately before a comma, semicolon, or colon.
                          
                          Okay: spam(ham[1], {eggs: 2})
                          E201: spam( ham[1], {eggs: 2})
                          E201: spam(ham[ 1], {eggs: 2})
                          E201: spam(ham[1], { eggs: 2})
                          E202: spam(ham[1], {eggs: 2} )
                          E202: spam(ham[1 ], {eggs: 2})
                          E202: spam(ham[1], {eggs: 2 })
                          
                          E203: if x == 4: print x, y; x, y = y , x
                          E203: if x == 4: print x, y ; x, y = y, x
                          E203: if x == 4 : print x, y; x, y = y, x

                          Whitespace before ']'
                          Open

                              S2 = secret[ int(math.floor(len(secret)/2.0)) : ]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Avoid extraneous whitespace.

                          Avoid extraneous whitespace in these situations:
                          - Immediately inside parentheses, brackets or braces.
                          - Immediately before a comma, semicolon, or colon.
                          
                          Okay: spam(ham[1], {eggs: 2})
                          E201: spam( ham[1], {eggs: 2})
                          E201: spam(ham[ 1], {eggs: 2})
                          E201: spam(ham[1], { eggs: 2})
                          E202: spam(ham[1], {eggs: 2} )
                          E202: spam(ham[1 ], {eggs: 2})
                          E202: spam(ham[1], {eggs: 2 })
                          
                          E203: if x == 4: print x, y; x, y = y , x
                          E203: if x == 4: print x, y ; x, y = y, x
                          E203: if x == 4 : print x, y; x, y = y, x

                          Expected 2 blank lines, found 1
                          Open

                          def PRF_1_2(secret, label, seed, length):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          At least two spaces before inline comment
                          Open

                                  A = bytearray([ord('A')+x] * (x+1)) # 'A', 'BB', 'CCC', etc..
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate inline comments by at least two spaces.

                          An inline comment is a comment on the same line as a statement.
                          Inline comments should be separated by at least two spaces from the
                          statement. They should start with a # and a single space.
                          
                          Each line of a block comment starts with a # and a single space
                          (unless it is indented text inside the comment).
                          
                          Okay: x = x + 1  # Increment x
                          Okay: x = x + 1    # Increment x
                          Okay: # Block comment
                          E261: x = x + 1 # Increment x
                          E262: x = x + 1  #Increment x
                          E262: x = x + 1  #  Increment x
                          E265: #Block comment
                          E266: ### Block comment

                          Block comment should start with '# '
                          Open

                              #Run the left half through P_MD5 and the right half through P_SHA1
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate inline comments by at least two spaces.

                          An inline comment is a comment on the same line as a statement.
                          Inline comments should be separated by at least two spaces from the
                          statement. They should start with a # and a single space.
                          
                          Each line of a block comment starts with a # and a single space
                          (unless it is indented text inside the comment).
                          
                          Okay: x = x + 1  # Increment x
                          Okay: x = x + 1    # Increment x
                          Okay: # Block comment
                          E261: x = x + 1 # Increment x
                          E262: x = x + 1  #Increment x
                          E262: x = x + 1  #  Increment x
                          E265: #Block comment
                          E266: ### Block comment

                          Block comment should start with '# '
                          Open

                              #XOR the output values and return the result
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate inline comments by at least two spaces.

                          An inline comment is a comment on the same line as a statement.
                          Inline comments should be separated by at least two spaces from the
                          statement. They should start with a # and a single space.
                          
                          Each line of a block comment starts with a # and a single space
                          (unless it is indented text inside the comment).
                          
                          Okay: x = x + 1  # Increment x
                          Okay: x = x + 1    # Increment x
                          Okay: # Block comment
                          E261: x = x + 1 # Increment x
                          E262: x = x + 1  #Increment x
                          E262: x = x + 1  #  Increment x
                          E265: #Block comment
                          E266: ### Block comment

                          Expected 2 blank lines, found 1
                          Open

                          @deprecated_method("Please use calc_key function instead.")
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Whitespace after '['
                          Open

                              S2 = secret[ int(math.floor(len(secret)/2.0)) : ]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Avoid extraneous whitespace.

                          Avoid extraneous whitespace in these situations:
                          - Immediately inside parentheses, brackets or braces.
                          - Immediately before a comma, semicolon, or colon.
                          
                          Okay: spam(ham[1], {eggs: 2})
                          E201: spam( ham[1], {eggs: 2})
                          E201: spam(ham[ 1], {eggs: 2})
                          E201: spam(ham[1], { eggs: 2})
                          E202: spam(ham[1], {eggs: 2} )
                          E202: spam(ham[1 ], {eggs: 2})
                          E202: spam(ham[1], {eggs: 2 })
                          
                          E203: if x == 4: print x, y; x, y = y , x
                          E203: if x == 4: print x, y ; x, y = y, x
                          E203: if x == 4 : print x, y; x, y = y, x

                          Whitespace before ':'
                          Open

                              S2 = secret[ int(math.floor(len(secret)/2.0)) : ]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Avoid extraneous whitespace.

                          Avoid extraneous whitespace in these situations:
                          - Immediately inside parentheses, brackets or braces.
                          - Immediately before a comma, semicolon, or colon.
                          
                          Okay: spam(ham[1], {eggs: 2})
                          E201: spam( ham[1], {eggs: 2})
                          E201: spam(ham[ 1], {eggs: 2})
                          E201: spam(ham[1], { eggs: 2})
                          E202: spam(ham[1], {eggs: 2} )
                          E202: spam(ham[1 ], {eggs: 2})
                          E202: spam(ham[1], {eggs: 2 })
                          
                          E203: if x == 4: print x, y; x, y = y , x
                          E203: if x == 4: print x, y ; x, y = y, x
                          E203: if x == 4 : print x, y; x, y = y, x

                          Expected 2 blank lines, found 1
                          Open

                          def PRF_1_2_SHA384(secret, label, seed, length):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Continuation line under-indented for visual indent
                          Open

                                                      clientRandom + serverRandom, 48)
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Continuation lines indentation.

                          Continuation lines should align wrapped elements either vertically
                          using Python's implicit line joining inside parentheses, brackets
                          and braces, or using a hanging indent.
                          
                          When using a hanging indent these considerations should be applied:
                          - there should be no arguments on the first line, and
                          - further indentation should be used to clearly distinguish itself
                            as a continuation line.
                          
                          Okay: a = (\n)
                          E123: a = (\n    )
                          
                          Okay: a = (\n    42)
                          E121: a = (\n   42)
                          E122: a = (\n42)
                          E123: a = (\n    42\n    )
                          E124: a = (24,\n     42\n)
                          E125: if (\n    b):\n    pass
                          E126: a = (\n        42)
                          E127: a = (24,\n      42)
                          E128: a = (24,\n    42)
                          E129: if (a or\n    b):\n    pass
                          E131: a = (\n    42\n 24)

                          Missing whitespace after ','
                          Open

                              elif version in ((3,1), (3,2)):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Missing whitespace after ','
                          Open

                              elif version in ((3,1), (3,2)):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Trailing whitespace
                          Open

                          # Authors: 
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Trailing whitespace is superfluous.

                          The warning returned varies on whether the line itself is blank,
                          for easier filtering for those who want to indent their blank lines.
                          
                          Okay: spam(1)\n#
                          W291: spam(1) \n#
                          W293: class Foo(object):\n    \n    bang = 12

                          Missing whitespace after ','
                          Open

                              if version == (3,0):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Block comment should start with '# '
                          Open

                          #This function is used by VerifierDB.makeVerifier
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate inline comments by at least two spaces.

                          An inline comment is a comment on the same line as a statement.
                          Inline comments should be separated by at least two spaces from the
                          statement. They should start with a # and a single space.
                          
                          Each line of a block comment starts with a # and a single space
                          (unless it is indented text inside the comment).
                          
                          Okay: x = x + 1  # Increment x
                          Okay: x = x + 1    # Increment x
                          Okay: # Block comment
                          E261: x = x + 1 # Increment x
                          E262: x = x + 1  #Increment x
                          E262: x = x + 1  #  Increment x
                          E265: #Block comment
                          E266: ### Block comment

                          Missing whitespace after ','
                          Open

                              g,N = goodGroupParameters[bitsIndex]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Missing whitespace after ','
                          Open

                              elif version == (3,3):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Expected 2 blank lines, found 1
                          Open

                          def makeU(N, A, B):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Expected 2 blank lines, found 1
                          Open

                          @deprecated_method("Please use calc_key function instead.")
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Missing whitespace after ','
                          Open

                              if version == (3,0):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Missing whitespace after ','
                          Open

                                  if version in ((3,1), (3,2)):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Continuation line under-indented for visual indent
                          Open

                                              b"client finished"]:
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Continuation lines indentation.

                          Continuation lines should align wrapped elements either vertically
                          using Python's implicit line joining inside parentheses, brackets
                          and braces, or using a hanging indent.
                          
                          When using a hanging indent these considerations should be applied:
                          - there should be no arguments on the first line, and
                          - further indentation should be used to clearly distinguish itself
                            as a continuation line.
                          
                          Okay: a = (\n)
                          E123: a = (\n    )
                          
                          Okay: a = (\n    42)
                          E121: a = (\n   42)
                          E122: a = (\n42)
                          E123: a = (\n    42\n    )
                          E124: a = (24,\n     42\n)
                          E125: if (\n    b):\n    pass
                          E126: a = (\n        42)
                          E127: a = (24,\n      42)
                          E128: a = (24,\n    42)
                          E129: if (a or\n    b):\n    pass
                          E131: a = (\n    42\n 24)

                          Missing whitespace after ':'
                          Open

                              bitsIndex = {1024:0, 1536:1, 2048:2, 3072:3, 4096:4, 6144:5, 8192:6}[bits]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Expected 2 blank lines, found 1
                          Open

                          def makeK(N, g):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Expected 2 blank lines, found 1
                          Open

                          def createHMAC(k, digestmod=hashlib.sha1):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Indentation is not a multiple of 4
                          Open

                            return bytesToNumber(SHA1(PAD(N, A) + PAD(N, B)))
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Use indent_size (PEP8 says 4) spaces per indentation level.

                          For really old code that you don't want to mess up, you can continue
                          to use 8-space tabs.
                          
                          Okay: a = 1
                          Okay: if a == 0:\n    a = 1
                          E111:   a = 1
                          E114:   # a = 1
                          
                          Okay: for item in items:\n    pass
                          E112: for item in items:\npass
                          E115: for item in items:\n# Hi\n    pass
                          
                          Okay: a = 1\nb = 2
                          E113: a = 1\n    b = 2
                          E116: a = 1\n    # b = 2

                          At least two spaces before inline comment
                          Open

                                  else: # version == (3,3):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate inline comments by at least two spaces.

                          An inline comment is a comment on the same line as a statement.
                          Inline comments should be separated by at least two spaces from the
                          statement. They should start with a # and a single space.
                          
                          Each line of a block comment starts with a # and a single space
                          (unless it is indented text inside the comment).
                          
                          Okay: x = x + 1  # Increment x
                          Okay: x = x + 1    # Increment x
                          Okay: # Block comment
                          E261: x = x + 1 # Increment x
                          E262: x = x + 1  #Increment x
                          E262: x = x + 1  #  Increment x
                          E265: #Block comment
                          E266: ### Block comment

                          Too many blank lines (2)
                          Open

                              # SSL3 calculations.
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Missing whitespace after ':'
                          Open

                              bitsIndex = {1024:0, 1536:1, 2048:2, 3072:3, 4096:4, 6144:5, 8192:6}[bits]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Indentation is not a multiple of 4
                          Open

                            return bytesToNumber(SHA1(numberToByteArray(N) + PAD(N, g)))
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Use indent_size (PEP8 says 4) spaces per indentation level.

                          For really old code that you don't want to mess up, you can continue
                          to use 8-space tabs.
                          
                          Okay: a = 1
                          Okay: if a == 0:\n    a = 1
                          E111:   a = 1
                          E114:   # a = 1
                          
                          Okay: for item in items:\n    pass
                          E112: for item in items:\npass
                          E115: for item in items:\n# Hi\n    pass
                          
                          Okay: a = 1\nb = 2
                          E113: a = 1\n    b = 2
                          E116: a = 1\n    # b = 2

                          Missing whitespace around operator
                          Open

                              if len(salt)>=256:
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Surround operators with a single space on either side.

                          - Always surround these binary operators with a single space on
                            either side: assignment (=), augmented assignment (+=, -= etc.),
                            comparisons (==, <, >, !=, <=, >=, in, not in, is, is not),
                            Booleans (and, or, not).
                          
                          - If operators with different priorities are used, consider adding
                            whitespace around the operators with the lowest priorities.
                          
                          Okay: i = i + 1
                          Okay: submitted += 1
                          Okay: x = x * 2 - 1
                          Okay: hypot2 = x * x + y * y
                          Okay: c = (a + b) * (a - b)
                          Okay: foo(bar, key='word', *args, **kwargs)
                          Okay: alpha[:-i]
                          
                          E225: i=i+1
                          E225: submitted +=1
                          E225: x = x /2 - 1
                          E225: z = x **y
                          E225: z = 1and 1
                          E226: c = (a+b) * (a-b)
                          E226: hypot2 = x*x + y*y
                          E227: c = a|b
                          E228: msg = fmt%(errno, errmsg)

                          Missing whitespace after ':'
                          Open

                              bitsIndex = {1024:0, 1536:1, 2048:2, 3072:3, 4096:4, 6144:5, 8192:6}[bits]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Continuation line over-indented for visual indent
                          Open

                                                      clientRandom + serverRandom, 48)
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Continuation lines indentation.

                          Continuation lines should align wrapped elements either vertically
                          using Python's implicit line joining inside parentheses, brackets
                          and braces, or using a hanging indent.
                          
                          When using a hanging indent these considerations should be applied:
                          - there should be no arguments on the first line, and
                          - further indentation should be used to clearly distinguish itself
                            as a continuation line.
                          
                          Okay: a = (\n)
                          E123: a = (\n    )
                          
                          Okay: a = (\n    42)
                          E121: a = (\n   42)
                          E122: a = (\n42)
                          E123: a = (\n    42\n    )
                          E124: a = (24,\n     42\n)
                          E125: if (\n    b):\n    pass
                          E126: a = (\n        42)
                          E127: a = (24,\n      42)
                          E128: a = (24,\n    42)
                          E129: if (a or\n    b):\n    pass
                          E131: a = (\n    42\n 24)

                          Missing whitespace after ':'
                          Open

                              bitsIndex = {1024:0, 1536:1, 2048:2, 3072:3, 4096:4, 6144:5, 8192:6}[bits]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Block comment should start with '# '
                          Open

                              #Split the secret into left and right halves
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate inline comments by at least two spaces.

                          An inline comment is a comment on the same line as a statement.
                          Inline comments should be separated by at least two spaces from the
                          statement. They should start with a # and a single space.
                          
                          Each line of a block comment starts with a # and a single space
                          (unless it is indented text inside the comment).
                          
                          Okay: x = x + 1  # Increment x
                          Okay: x = x + 1    # Increment x
                          Okay: # Block comment
                          E261: x = x + 1 # Increment x
                          E262: x = x + 1  #Increment x
                          E262: x = x + 1  #  Increment x
                          E265: #Block comment
                          E266: ### Block comment

                          Expected 2 blank lines, found 1
                          Open

                          def PRF_SSL(secret, seed, length):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Missing whitespace after ':'
                          Open

                              bitsIndex = {1024:0, 1536:1, 2048:2, 3072:3, 4096:4, 6144:5, 8192:6}[bits]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Expected 2 blank lines, found 1
                          Open

                          def createMAC_SSL(k, digestmod=None):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Expected 2 blank lines, found 1
                          Open

                          def makeVerifier(username, password, bits):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Missing whitespace around operator
                          Open

                              if len(username)>=256:
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Surround operators with a single space on either side.

                          - Always surround these binary operators with a single space on
                            either side: assignment (=), augmented assignment (+=, -= etc.),
                            comparisons (==, <, >, !=, <=, >=, in, not in, is, is not),
                            Booleans (and, or, not).
                          
                          - If operators with different priorities are used, consider adding
                            whitespace around the operators with the lowest priorities.
                          
                          Okay: i = i + 1
                          Okay: submitted += 1
                          Okay: x = x * 2 - 1
                          Okay: hypot2 = x * x + y * y
                          Okay: c = (a + b) * (a - b)
                          Okay: foo(bar, key='word', *args, **kwargs)
                          Okay: alpha[:-i]
                          
                          E225: i=i+1
                          E225: submitted +=1
                          E225: x = x /2 - 1
                          E225: z = x **y
                          E225: z = 1and 1
                          E226: c = (a+b) * (a-b)
                          E226: hypot2 = x*x + y*y
                          E227: c = a|b
                          E228: msg = fmt%(errno, errmsg)

                          Missing whitespace after ':'
                          Open

                              bitsIndex = {1024:0, 1536:1, 2048:2, 3072:3, 4096:4, 6144:5, 8192:6}[bits]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Expected 2 blank lines, found 1
                          Open

                          def PAD(n, x):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Missing whitespace after ','
                          Open

                                  if version in ((3,1), (3,2)):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Continuation line under-indented for visual indent
                          Open

                                      client_random=None, server_random=None, output_length=None):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Continuation lines indentation.

                          Continuation lines should align wrapped elements either vertically
                          using Python's implicit line joining inside parentheses, brackets
                          and braces, or using a hanging indent.
                          
                          When using a hanging indent these considerations should be applied:
                          - there should be no arguments on the first line, and
                          - further indentation should be used to clearly distinguish itself
                            as a continuation line.
                          
                          Okay: a = (\n)
                          E123: a = (\n    )
                          
                          Okay: a = (\n    42)
                          E121: a = (\n   42)
                          E122: a = (\n42)
                          E123: a = (\n    42\n    )
                          E124: a = (24,\n     42\n)
                          E125: if (\n    b):\n    pass
                          E126: a = (\n        42)
                          E127: a = (24,\n      42)
                          E128: a = (24,\n    42)
                          E129: if (a or\n    b):\n    pass
                          E131: a = (\n    42\n 24)

                          Continuation line under-indented for visual indent
                          Open

                                              b"client finished"]:
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Continuation lines indentation.

                          Continuation lines should align wrapped elements either vertically
                          using Python's implicit line joining inside parentheses, brackets
                          and braces, or using a hanging indent.
                          
                          When using a hanging indent these considerations should be applied:
                          - there should be no arguments on the first line, and
                          - further indentation should be used to clearly distinguish itself
                            as a continuation line.
                          
                          Okay: a = (\n)
                          E123: a = (\n    )
                          
                          Okay: a = (\n    42)
                          E121: a = (\n   42)
                          E122: a = (\n42)
                          E123: a = (\n    42\n    )
                          E124: a = (24,\n     42\n)
                          E125: if (\n    b):\n    pass
                          E126: a = (\n        42)
                          E127: a = (24,\n      42)
                          E128: a = (24,\n    42)
                          E129: if (a or\n    b):\n    pass
                          E131: a = (\n    42\n 24)

                          Missing whitespace after ':'
                          Open

                              bitsIndex = {1024:0, 1536:1, 2048:2, 3072:3, 4096:4, 6144:5, 8192:6}[bits]
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Each comma, semicolon or colon should be followed by whitespace.

                          Okay: [a, b]
                          Okay: (3,)
                          Okay: a[1:4]
                          Okay: a[:4]
                          Okay: a[1:]
                          Okay: a[1:4:2]
                          E231: ['a','b']
                          E231: foo(bar,baz)
                          E231: [{'a':'b'}]

                          Expected 2 blank lines, found 1
                          Open

                          def calc_key(version, secret, cipher_suite, label, handshake_hashes=None,
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          Expected 2 blank lines, found 1
                          Open

                          def makeX(salt, username, password):
                          Severity: Minor
                          Found in tlslite/mathtls.py by pep8

                          Separate top-level function and class definitions with two blank lines.

                          Method definitions inside a class are separated by a single blank
                          line.
                          
                          Extra blank lines may be used (sparingly) to separate groups of
                          related functions.  Blank lines may be omitted between a bunch of
                          related one-liners (e.g. a set of dummy implementations).
                          
                          Use blank lines in functions, sparingly, to indicate logical
                          sections.
                          
                          Okay: def a():\n    pass\n\n\ndef b():\n    pass
                          Okay: def a():\n    pass\n\n\nasync def b():\n    pass
                          Okay: def a():\n    pass\n\n\n# Foo\n# Bar\n\ndef b():\n    pass
                          Okay: default = 1\nfoo = 1
                          Okay: classify = 1\nfoo = 1
                          
                          E301: class Foo:\n    b = 0\n    def bar():\n        pass
                          E302: def a():\n    pass\n\ndef b(n):\n    pass
                          E302: def a():\n    pass\n\nasync def b(n):\n    pass
                          E303: def a():\n    pass\n\n\n\ndef b(n):\n    pass
                          E303: def a():\n\n\n\n    pass
                          E304: @decorator\n\ndef a():\n    pass
                          E305: def a():\n    pass\na()
                          E306: def a():\n    def b():\n        pass\n    def c():\n        pass

                          There are no issues that match your filters.

                          Category
                          Status