-
Notifications
You must be signed in to change notification settings - Fork 392
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
[Subtask] Add Pylint Rules for client-python naming rules #3205
Labels
subtask
Subtasks of umbrella issue
Comments
noidname01
changed the title
[Subtask] Add Pylint Rules for client-python naming and spacing rules
[Subtask] Add Pylint Rules for client-python naming rules
Apr 30, 2024
2 tasks
jerryshao
pushed a commit
that referenced
this issue
May 13, 2024
…-python (#3369) ### What changes were proposed in this pull request? - Define naming style of each class, module, function and variable - See `pylintrc` for detail settings ### Why are the changes needed? Fix: #3205 ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? No --------- Co-authored-by: TimWang <tim.wang@pranaq.com>
github-actions bot
pushed a commit
that referenced
this issue
May 13, 2024
…-python (#3369) ### What changes were proposed in this pull request? - Define naming style of each class, module, function and variable - See `pylintrc` for detail settings ### Why are the changes needed? Fix: #3205 ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? No --------- Co-authored-by: TimWang <tim.wang@pranaq.com>
yuqi1129
pushed a commit
that referenced
this issue
May 14, 2024
…-python (#3372) <!-- 1. Title: [#<issue>] <type>(<scope>): <subject> Examples: - "[#123] feat(operator): support xxx" - "[#233] fix: check null before access result in xxx" - "[MINOR] refactor: fix typo in variable name" - "[MINOR] docs: fix typo in README" - "[#255] test: fix flaky test NameOfTheTest" Reference: https://www.conventionalcommits.org/en/v1.0.0/ 2. If the PR is unfinished, please mark this PR as draft. --> ### What changes were proposed in this pull request? - Define naming style of each class, module, function and variable - See `pylintrc` for detail settings ### Why are the changes needed? Fix: #3205 ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? No Co-authored-by: noidname01 <55401762+noidname01@users.noreply.github.com> Co-authored-by: TimWang <tim.wang@pranaq.com>
diqiu50
pushed a commit
to diqiu50/gravitino
that referenced
this issue
Jun 13, 2024
…client-python (apache#3369) ### What changes were proposed in this pull request? - Define naming style of each class, module, function and variable - See `pylintrc` for detail settings ### Why are the changes needed? Fix: apache#3205 ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? No --------- Co-authored-by: TimWang <tim.wang@pranaq.com>
coolderli
pushed a commit
that referenced
this issue
Dec 17, 2024
…-python (#3369) ### What changes were proposed in this pull request? - Define naming style of each class, module, function and variable - See `pylintrc` for detail settings ### Why are the changes needed? Fix: #3205 ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? No --------- Co-authored-by: TimWang <tim.wang@pranaq.com> (cherry picked from commit 0a3caed)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the subtask
Parent issue
#3203
The text was updated successfully, but these errors were encountered: