-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
CI: run pydocstyle with our custom options #17145
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
CI: run pydocstyle with our custom options #17145
Conversation
3b2e153
to
b859a67
Compare
Based on the CI results, I would recommend adding For context, now that (Again, there was nothing removed from the
|
70e7dff
to
ff9da09
Compare
ff9da09
to
f1b8705
Compare
Tried to remove the
|
Looks like this commit should wait on #17143 (or vice-versa, that PR should add |
PR Summary
Fixes #17141, so that we can add extra individual errors to our flake8-docstrings (really, pydocstyle) check, especially
D213
, per this week's call.Per the discussion on https://gitlab.com/pycqa/flake8-docstrings/-/issues/43, the intended solution is currently for us to list all the
numpy
-style error codes manually in ourselect
block in.flake8
, then add extra ones as needed.In order to get the extra non-
numpy
codes to work, we have to use the (currently undocumented, but see https://gitlab.com/pycqa/flake8-docstrings/-/merge_requests/27) special catch-all flag,--docstring-convention=all
.Just for the record, the full list of non
--docstring-convention=numpy
error codes that we could choose to turn on is: D107, D203, D212, D213, D402, D413, D415, D416, and D417.Their meanings can be found at http://www.pydocstyle.org/en/latest/error_codes.html.
PR Checklist