Github user holdenk commented on the issue:

    https://github.com/apache/spark/pull/14963
  
    This PR does somehting useful by its self namely it uses virtual env / 
`requirements.txt` to fix the versions of `pylint` and `pep8` and reenables 
`pylint` checking of the code. There is a setup cost associated with installing 
the virtual env the first time we run this, but only for developers who run 
`./dev/pylint`.
    
    Since this changes effectively adds back some linter rules its possible 
that mainline has changed since the last jenkins run and a merge to master 
performs poorly. Thinking about it some more, since we aren't under a rush for 
this, I'd like to double check this on Tuesday/Thursday on some of my coworkers 
machines that run OSX just to be safe because I know we've had some differences 
in the past with linter behaviour their (although this PR should remove those 
differences going forward its probably not a bad idea to double check).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to