It is recommended to properly indent docstrings for readability.
Cipher used is not secure. It is recommended to replace with a known secure cipher such as AES.
Detected the use of one of the C-style pre/post increment or decrement operators, --
and ++
, which don't exist in Python.
Use the +=
or -=
operators instead.
D2, MD4, MD5, SHA1 signature algorithms are known to be vulnerable to collision attacks. Attackers can exploit this to generate another certificate with the same digital signature, allowing them to masquerade as the affected service.
There should be only one space after the ,
character.
A continuation line is indented farther than it should be for a hanging indent.
Protocol
members TYP-031All members of a protocol are required to have explicitly declared types. You can read more about it in this PEP
@staticmethod
PYL-R0201The method doesn't use its bound instance. Decorate this method with @staticmethod
decorator, so that Python does not have to instantiate a bound method for every instance of this class thereby saving memory and computation. Read more about staticmethods here.
Comment indentation should be a multiple of four.
Debuggers should only be used temporarily and locally. It is highly recommended to remove debug statements in checked-in code.
A visual indented line has the same indentation as the next logical line. This can make it hard to read.
The type of a Type
variable can not be declared. It is recommended to remove it.
pass
statement PYL-W0107The pass
statement used here is not necessary. You can safely remove this.
It is recommended to use spaces in the docstrings, just as the code.
It is recommended to put a newline at the end of the file.
The class is using, as a metaclass, something which might be invalid for using as a metaclass.
Comments should be indented relative to the code in the block they are in.
Type hint is unreliable for the with
statement. Please check the issue occurrence message for details.
__all__
TYP-056Type of __all__
must be sequence string. See the issue message for more details
A type hint is expected within[...]
. It is recommended to abide by this convention.