This repository has been archived by the owner on Nov 3, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
EDIT: I understand your format is some custom one, not the Google one. So not sure, maybe this should be closed, or maybe everything should be conformed to
Args
?I've written custom parsers and emitters for everything from docstrings to classes and functions. However, I recently came across an issue with the TensorFlow codebase: inconsistent use of
Args:
andArguments:
in its docstrings. It is easy enough to extend my parsers to support both variants, however it looks likeArguments:
is wrong anyway, as per:https://google.github.io/styleguide/pyguide.html#doc-function-args @
ddccc0f
https://chromium.googlesource.com/chromiumos/docs/+/master/styleguide/python.md#describing-arguments-in-docstrings @
9fc0fc0
https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html @
c0ae8e3
Therefore, only
Args:
is valid. This PR replaces them throughout the codebase.PS: For related PRs, see tensorflow/tensorflow/pull/45420