Open mdemoret-nv opened 3 years ago
This issue has been labeled inactive-30d
due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d
if there is no activity in the next 60 days.
@mdemoret-nv @teju85 I wish to work on this issue! Could you please give me some pointers?
This issue has been labeled inactive-90d
due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.
Since the python documentation isn't built for PRs, many docstring issues get committed into the active branch and are only caught right before release. There are flake8 extensions which can check docstrings for errors and flag them during the style check.
Two extensions that I have in mind are
flake8-docstrings
andflake8-rst-docstrings
. These can be added to flake8 withEnabling these plugins and running flake8 generates 2793 errors as of 0.19. Many of these are true positives but are overly strict for our needs. Adding the following to
setup.cfg
, significantly reduces the noise:Many of these docstring issues have been hidden by the fact that they aren't included in the Sphinx documentation. Adding these plugins would help reduce those errors in the future.
For reference, here is a sample of the output: