Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2222#issuecomment-53997266
At least for Jenkins, one option it to use `git ls-files` to find all
Python files tracked by Git. I'm not sure whether this would be confusing to
developers who are testing locally, since they might write a few new Python
file, run the linter, then add and commit the new files, causing the new file
to be missed. Maybe a compromise would be to only test files tracked by git
and print a loud warning for unchecked files that aren't on a blacklist. This
is probably massive overengineering, though. It's rare that we add Python
files in new locations, so it's probably simpler to just test a fixed set of
files/locations.
---
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]
