Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7241#issuecomment-119698212
I like your suggestion of disabling most of the warnings for now, then
gradually re-enabling them in followup patches.
Is pylint currently configured to treat all warnings as errors (e.g. fail
the linter if a warning is printed)? If not, I think we should go ahead and
switch to that fail-fast behavior so that we don't unknowingly introduce new
violations. Once we get that basic infra in place, we can commit this and
iterate on enabling more warnings.
---
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]
