Skip to content

Increase Pylint Score for the current codebase #4557

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.

Sign up for GitHub

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

Jump to bottom
Open
4 tasks
RishabhJain2018 opened this issue Apr 3, 2025 · 6 comments · May be fixed by #4616 or #4618
Open
4 tasks

Increase Pylint Score for the current codebase #4557

RishabhJain2018 opened this issue Apr 3, 2025 · 6 comments · May be fixed by #4616 or #4618
Assignees
@donburi82 @Akshat453 @abhishekaj28
Labels
backend CI easy_to_fix enhancement good first issue GSOC-2025

Comments

@RishabhJain2018
Copy link
Member

RishabhJain2018 commented Apr 3, 2025 •
edited
Loading

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

Objectives

  1. Identify and fix common pylint errors and warnings
  2. Increase the overall pylint score from current level to at least 7.5
  3. 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
  1. First fix all error-level issues (--errors-only)
  2. Then address warning-level issues
  3. Finally work on convention and refactor messages
@donburi82
Copy link
Contributor

I would like to work on this issue! @RishabhJain2018

@RishabhJain2018
Copy link
Member Author

Hey @donburi82 , Sure. It is big issue, so multiple people can work on this. Please open the PR for each module fixes.

@Akshat453
Copy link
Contributor

Hey @RishabhJain2018 can i work on one of the modules?

This was referenced Apr 4, 2025
Merged
Open
@donburi82 donburi82 mentioned this issue Apr 5, 2025
Merged
@abhishekaj28
Copy link

hey @RishabhJain2018, I would like to work on this issue, if it's not assigned to anyone !!

@RishabhJain2018
Copy link
Member Author

Sure, please look at the current PRs and pick the ones for which no PR is opened so that work is not duplicated.

@abhishekaj28
Copy link

abhishekaj28 commented Apr 8, 2025 •
edited
Loading

yeah yeah got it!! Thank you @RishabhJain2018

@abhishekaj28 abhishekaj28 mentioned this issue Apr 8, 2025
Closed
@Akshat453 Akshat453 mentioned this issue Apr 14, 2025
Open
This was referenced Apr 27, 2025
Open
Open
Open
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@donburi82 donburi82

@Akshat453 Akshat453

@abhishekaj28 abhishekaj28

Labels
backend CI easy_to_fix enhancement good first issue GSOC-2025
Projects
None yet
Milestone
No milestone
4 participants
@RishabhJain2018 @donburi82 @Akshat453 @abhishekaj28