-
Notifications
You must be signed in to change notification settings - Fork 324
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
[*.py] Rename "Arguments:" to "Args:" #604
base: master
Are you sure you want to change the base?
[*.py] Rename "Arguments:" to "Args:" #604
Conversation
Thank you for your contribution @SamuelMarks, and sorry for taking so long to review this. Could you please update this PR to cover recently merged [experimental](https://github.com/tensorflow/model-optimization/tree/master/tensorflow_model_optimization/python/core/clustering/keras/experimental modules)? @daverim, please review this change. |
0867601
to
4f4e5d0
Compare
@akarmi That should do the trick |
Thank you! LGTM. |
@daverim, please check this change. |
1e79b7c
to
53d2425
Compare
@akarmi Okay I merged in master (again) |
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