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

Some pylint naming checks are too strict #256

Closed
marcpaterno opened this issue Apr 18, 2023 · 0 comments · Fixed by #257
Closed

Some pylint naming checks are too strict #256

marcpaterno opened this issue Apr 18, 2023 · 0 comments · Fixed by #257

Comments

@marcpaterno
Copy link
Collaborator

Some of the pylint naming checks are too strict. We should globally allow non-snake-case variable, argument, and attribute names because often the names natural in the scientific domain do not fit the snake-case naming convention.

When we globally allow these names, we should remove the “pylint: disable...” instructions in the code that were allowing them to pass until now. That will help remaining “pylint: disable” commands stand out more clearly, as they should.

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 a pull request may close this issue.

1 participant