Sambhav Kothari

Separately - it would have been great if we could have versions also driven by the Github tags instead having to manually bump them similar to https://github.com/cruft/cruft/blob/0c6de85d974197969c0e65913857eaa36b788e5e/.github/workflows/pypi_publish.yml#L22 but any improvement...

We only support Google and numpy styles for argument verification. If you can provide a standard way to write restructured docstrings (pep257) with args, I'd be happy to add support...

@Pierre-Sassoulas that sounds great! I am away on vacations for the next few weeks so I might be slow to respond but if you send over a github actions PR,...

@aphedges has also graciously volunteered to help out with the triage and review process. I have added them with `triage` permissions to the repository to help with issue and PR...

Not sure - but it isn't straightfoward afaict - it would involve updating https://github.com/PyCQA/pydocstyle/blob/master/src/pydocstyle/parser.py to support cython. Currently we heavily rely on the tokenize module to parse files, we also...

@heoga thank you so much for this PR! Sorry for the late review. Would it be possible for you to rebase this PR against the latest changes in the master...

Yeah - the issue is related to how we treat conventions as a bundle of error codes, instead of a first class entity. If we indeed take advantage of the...

@thejcannon could you please rebase this PR against the master branch? Thanks!

@saroad2 I am starting work on pydocstyle 6.0 which will elevate conventions to be a first class concept in the checker. I'd be more than happy to have other contributors...

> Any progress on this? It's quite puzzling to run into this, because there's no indication on what/where the error is, just a big fat python backtrace. I plan to...