It is recommended to properly indent docstrings for readability.
It is recommended to use spaces in the docstrings, just as the code.
Module docstring is missing. If you want to ignore this, you can configure this in the .deepsource.toml
file. Please refer to docs for available options.
There shouldn't be any blank lines before the class docstring. Remove the blank lines to fix this issue.
There should be exactly one blank line after the class docstring.
If there are backslashes in a docstring, please use raw strings.
It is recommended to properly indent docstrings for readability.
Class docstring is missing. If you want to ignore this, you can configure this in the .deepsource.toml
file. Please refer to docs for available options.
You should avoid spaces at the beginning and at the end of a docstring.
The module/function docstring is missing. If you want to ignore this, you can configure this in the .deepsource.toml
file. Please refer to docs for available options.
Use of triple-quotes is recommended to specify docstrings.
There shouldn't be any blank lines after the function docstring. Remove the blank lines to fix this issue.
There shouldn't be any blank lines before the function docstring. Remove the blank lines to fix this issue.
FIXME
/XXX
/TODO
encountered PYL-W0511You have marked this block as FIXME
/XXX
/TODO
. Please make sure this is addressed, or remove this comment as this could be misleading.
If a docstring fits in a single line (72 characters according to PEP8), it is recommended to have the quotes on the same line.
The first line of the function docstring has the function's signature, which is not recommended. It shouldn't be specified unless you're specifying or explaining something which might be confusing. It is recommended to remove the redundant function signature from the docstring.