Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7241#issuecomment-120096312
It looks like our comments raced slightly. I thought that our use of
Pylint with Python 3 might be leading to failures in Jenkins that did not occur
locally when running with Python 2. If the lint checks pass on Python 3 then
it may be okay to merge this. One concern, however, is whether allowing this to
run with the system's default Python version could lead to build failures down
the line if the Jenkins environment's default Python version were to change to
Python 2.
Fixing this by forcing a specific Python version to be used for running the
linter might be tricky because there's not an `easy-install2` executable; most
platforms only provide `easy-install2.X` where X is the minor version. I'm
sure that we could come up with a solution that works but this could get pretty
complicated. Maybe we can sidestep this if we can guarantee that passing the
pylint checks with Python 3 implies that they would pass under Python 2.
---
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]
