-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-23174][BUILD][PYTHON] python code style checker update #20338
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
Closed
Closed
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
e3677c9
Merge pull request #1 from apache/master
rekhajoshm 106fd8e
Merge pull request #2 from apache/master
rekhajoshm 0be142d
Merge pull request #3 from apache/master
rekhajoshm 6c6ee12
Merge pull request #4 from apache/master
rekhajoshm b123c60
Merge pull request #5 from apache/master
rekhajoshm c73c32a
Merge pull request #6 from apache/master
rekhajoshm 7dbf732
Merge pull request #8 from apache/master
rekhajoshm 5e9d718
Merge pull request #9 from apache/master
rekhajoshm 63d99b3
Merge pull request #10 from apache/master
rekhajoshm a7fc787
Merge pull request #11 from apache/master
rekhajoshm 8873441
[SPARK-11222][BUILD][PYTHON] python code style checker update
rekhajoshm 8718891
updated for review comment
rekhajoshm c386a9a
[SPARK-23174][BUILD][PYTHON] python code style checker update
rekhajoshm d10fbb4
updated nit
rekhajoshm 34a8590
updated for review comment
rekhajoshm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, do those
E722,E741,E305include rules to validate the blank line before starting doctests, which is described in the JIRA?Seems:
E722: "do not use bare except'"
E741: "ambiguous variable name 'l'",
E305: "expected 2 blank lines after class or function definition"
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These(E722, E741, E305) are new code style standards added that Spark seems to be violating.For now, added them in ignored.I have raised the doctest blank line as an issue under pep8, as it does not belong within Spark.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I asked this to double check if this PR fixes the issue linked JIRA. I think we could make another JIRA if this PR doesn't target to fix the linked JIRA.
For the best, it'd be nicer if you'd leave a issue link you raised under pep8 in
SPARK-11222, and open another JIRA about what this PR changes and then link it by fixing the PR title, if I understood you correctly.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated SPARK-11222. Added https://issues.apache.org/jira/browse/SPARK-23174.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we fix the code that violates
E722: "do not use bare except'"
E741: "ambiguous variable name 'l'",
E305: "expected 2 blank lines after class or function definition"
?
Or that's another PR/JIRA?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea .. there look actually many instances about it. I manually ran it against this PR. Will maybe take this one and open a PR separately after double checking each rule. Didn't take a look carefully yet.