Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exclude certain errors from pylint on tests. #3

Merged

Conversation

smspillaz
Copy link
Member

Don't report the following errors:

  • invalid-name: This is often triggered because test method names can
    be quite long. Descriptive test method names are good,
    so disable this warning.
  • super-on-old-class: unittest.TestCase is a new style class, but
    pylint detects an old style class.
  • too-many-public-methods: TestCase subclasses by definition have
    lots of methods.

Don't report the following errors:
 - invalid-name: This is often triggered because test method names can
                 be quite long. Descriptive test method names are good,
                 so disable this warning.
 - super-on-old-class: unittest.TestCase is a new style class, but
                       pylint detects an old style class.
 - too-many-public-methods: TestCase subclasses by definition have
                            lots of methods.
@smspillaz smspillaz force-pushed the polysquare-setuptools-lint.item_3 branch from acb1ac9 to 5797dda Compare April 17, 2015 02:36
smspillaz added a commit that referenced this pull request Apr 17, 2015
Exclude certain errors from pylint on tests.
@smspillaz smspillaz merged commit ff07142 into polysquare:master Apr 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant