-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
pylint score is too low #761
Comments
sounds good! |
Sure
Ready to contribute :) |
@cawibo are you still interested working on this? |
@ericklarac @keon I can work on this! Can I pick this up? |
Yes :) feel free to take any tasks you want |
The pylint score for this project is terribly low at 6.57. Many of the issues are non-issues for a project such as this, eg. broken naming conventions because of typical algorithm variable naming. However, there are still a ton of issues that should be dealt with, including but not limited to trailing whitespace, missing docstrings, dead code (after return), uncaught strings, and out-dated iteration using range with len.
Many of these issues could be taken care of automatically. I propose that we start with that.
The text was updated successfully, but these errors were encountered: