Cloud-CV
Increase Pylint Score for the current codebase
Improve Pylint Coverage and Code Quality in EvalAI
Description
We recently added pylint to our CI pipeline with a minimum score requirement of 5.0, but we need to improve our overall pylint score and fix common code quality issues throughout the codebase.
Current Status
- Pylint has been integrated into our Travis CI pipeline
- Current pylint score is below the acceptable threshold :(
- Refer here: https://app.travis-ci.com/github/Cloud-CV/EvalAI/jobs/631902183
- Multiple error categories are being reported that need fixing
Objectives
- Identify and fix common pylint errors and warnings
- Increase the overall pylint score from current level to at least 7.5
- Standardize code quality across the codebase
Proposed Tasks
- [ ] Address unused imports and variables (typically detected by C0410, W0611)
- [ ] Fix line length issues to comply with PEP 8 (79 characters)
- [ ] Add missing docstrings to modules, classes, and functions
- [ ] Fix poor variable naming and code style issues
- First fix all error-level issues (--errors-only)
- Then address warning-level issues
- Finally work on convention and refactor messages
Hey @donburi82 , Sure. It is big issue, so multiple people can work on this. Please open the PR for each module fixes.
hey @RishabhJain2018, I would like to work on this issue, if it's not assigned to anyone !!
Sure, please look at the current PRs and pick the ones for which no PR is opened so that work is not duplicated.
@RishabhJain2018 if issue is still available I would be happy to take it up!
@RishabhJain2018 if this issue is still open i would like like to work on this
@RishabhJain2018 if this issue is still open I would love to fix some issues on this
@RishabhJain2018 actually i have fixed some issues and willing to create pr for those fixes
