-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow running docstring checks via pydocstyle #86
Comments
Hello @StanczakDominik Thank you so much for using PEP8Speaks and considering to suggest an improvement. I am +1 for running pydocstyle. However, since they are not in "PEP8", let us keep the default option, not to check the docs, while it can be enabled by a configuration from Feel free to go ahead and work on this. I shall nevertheless consider working on this in the upcoming month sometime. |
All right! I'm starting to look through the code and tentatively make changes. I'm not too sure what the best way to test this out would be, but I guess I can probably mock some data and see how it behaves. |
@StanczakDominik Testing is definitely a pain in here. The way I do it is
That's quite a load of manual work. :( |
How about supporting this through flake8 extensions? There is flake8-docstrings. Also having support for flake8 extensions would make this tool generally extensible. So in the end this might be obsoleted once #56 is implemented. |
There's another package by the PyCQA called pydocstyle, which does basically the same thing as pycodestyle, except for docstrings. Unfortunately, it doesn't offer fixing bugs by itself, but it seems like it could potentially be a worthy addition to pep8speaks. Would you be interested in an implementation proposal (via PR)?
There's some more discussion started over at my main project ( PlasmaPy/PlasmaPy#276 where we considered running pydocstyle as a CI service).
The text was updated successfully, but these errors were encountered: