Skip to content

PEP-8 compliance: Requesting fewer pylint exception #4

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

Open
docktermj opened this issue Jul 5, 2023 · 0 comments
Open

PEP-8 compliance: Requesting fewer pylint exception #4

docktermj opened this issue Jul 5, 2023 · 0 comments

Comments

@docktermj
Copy link

When running pylint against output of

jtd-codegen --python-out ./python/typedef RFC8927.json

there are PEP-8 and python style exceptions returned by pylint. Examples:

  1. C0103: Argument name "s" doesn't conform to snake_case naming style (invalid-name)
  2. C0103: Variable name "tz" doesn't conform to snake_case naming style (invalid-name)
  3. C0114: Missing module docstring (missing-module-docstring)
  4. C0115: Missing class docstring (missing-class-docstring)
  5. C0116: Missing function or method docstring (missing-function-docstring)
  6. C0123: Use isinstance() rather than type() for a typecheck. (unidiomatic-typecheck)
  7. C0301: Line too long (113/100) (line-too-long)
  8. C0303: Trailing whitespace (trailing-whitespace)
  9. R0902: Too many instance attributes (8/7) (too-many-instance-attributes)
  10. R0914: Too many local variables (18/15) (too-many-locals)
  11. R0915: Too many statements (100/50) (too-many-statements)
  12. W1401: Anomalous backslash in string: '\d'. String constant might be missing an r prefix. (anomalous-backslash-in-string)

I realize some of these are unavoidable. However, if the output was a little cleaner it would make running GitHub Actions for testing (e.g. https://github.com/Senzing/g2-sdk-json-type-definition/blob/cc055ff2640c6ee76283bc66714fa8ce238fc99d/.github/workflows/pylint.yaml) a little nicer.

Thank you for your consideration of this.

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

No branches or pull requests

1 participant