The RAT and PEP8 checks don’t print a blank line after successful runs.
The scalastyle check shouldn’t either.

This guy just runs the pep8 utility on all code in the python
directory, minus cloudpickle, which is a 3rd-party library.

This guy just calls scalastyle.

Mostly done using autopep8, plus some hand fixes.

*fingers crossed*

I admit I’m not exactly sure how this works… Let’s see if I did the
right thing.

merge upstream changes

Minor, I know.

Everything looks cramped and it’s hard to tell at a glance where
sections begin. Adding a blank line between sections should fix that.

See the discussion here:
#1744 (comment)

Get the pep8 utility at runtime so that it’s not required to be
installed on the build server.

Don’t just assume curl got the file alright. Check and exit properly if
there were any problems.

“then” goes on the same line as the opening “if”.

merge upstream changes

No need to exclude files in the call to pep8. The tool references
tox.ini for config information, so we should use that.

“Undo” unnecessary line breaks introduced by accident when I called
autopep8 on the whole Python directory without setting the max line
length to 100. (autopep8 defaults to 79.)

[SPARK-1687] [PySpark] fix unit tests related to pickable namedtuple

PEP 8 is the bee’s knees.

merge upstream changes

merge upstream changes