-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-8706] [PySpark] [Project infra] Add pylint checks to PySpark #7241
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
9 commits
Select commit
Hold shift + click to select a range
7871bb1
[SPARK-8706] [PySpark] [Project infra] Add pylint checks to PySpark
MechCoder 8b8aa8a
Add pylint configuration file
MechCoder 1dbd094
Disable all checks for now
MechCoder 8498ff9
Remove blacklisted arguments and pointless statements check
MechCoder 71629f8
remove trailing whitespace
MechCoder ca8b749
Minor changes
MechCoder f3a5e17
undefined-variable
MechCoder 6d883a2
Silence warnings and make pylint tests fail to check if it works in j…
MechCoder 2fc7291
Remove pylint test fail
MechCoder 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
Oops, something went wrong.
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.
Should we put these somewhere outside of SPARK_HOME? Because we will call
git cleanin jenkins. It will be good if we could re-use the installed pylint.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.
AFAIK the PEP8 script currently suffers from this problem as well. I'm talking with Shane about configuring some per-build space which lives outside of the work directory that's cleaned by
git clean(I want to use these for holding separate.ivy2caches for each PRB workspace).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 this be done? What if the devloper does not want these pylint files outside the spark directory?