You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 3, 2023. It is now read-only.
I tried to use the script version from the "rewrite" branch. It seemed that the error numbers were changed and are not longer in sync with the README. This is expected, but there should be a way to ask the tool to describe all the possible errors.
A possible interface would be:
$ pep257 --error-list
D100: Module is missing docstring.
D101: Class is missing docstring.
...
Where if --explain is specified as well, the longer description is printed.
The text was updated successfully, but these errors were encountered:
Here's an actual use case - I want to use pep257.py as a mandatory part of our build system at work. However, we don't agree with all the rules of PEP257, so we would like to ignore some of the errors. It should be possible to get a list of them to go through, rather than just wait for an unwanted error to pop up and then dismiss it.
I tried to use the script version from the "rewrite" branch. It seemed that the error numbers were changed and are not longer in sync with the README. This is expected, but there should be a way to ask the tool to describe all the possible errors.
A possible interface would be:
Where if
--explain
is specified as well, the longer description is printed.The text was updated successfully, but these errors were encountered: