Repository: Cloud-CV/EvalAI
Issue: Increase Pylint Score for the current codebase
GitHub labels: enhancement

easy_to_fix

backend

good first issue

CI

GSOC-2025

# 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
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

I would like to work on this issue! @RishabhJain2018 

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

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

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.

yeah yeah got it!! Thank you @RishabhJain2018 


@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

hello @RishabhJain2018 can you check this pr ?? 


i would also like to work on this if the issue is still open!

Hi @RishabhJain2018 , I am interested in working on this issue to improve the pylint score. Is it currently open for contribution?
If it is available, please assign it to me. If it is already taken, I would appreciate any suggestions for other beginner-friendly issues I could pick up.
Thank you!

Hello @RishabhJain2018 , I’m interested in tackling this issue. Is it available to pick up? Please assign it to me if it’s free; otherwise, could you point me to other good starter issues? Thank you!



Hi @RishabhJain2018   
I’d like to contribute to this umbrella issue by improving pylint score for a specific module.

I’m planning to work on <apps/challenges> (or whichever you choose), focusing on:
- error-level pylint issues first
- then warnings (unused imports, naming, docstrings)

Please let me know if this module is still unclaimed. Thanks!


Hi @RishabhJain2018,  
I’d like to work on improving the pylint score for the `apps/accounts` module.  
Please let me know if this is fine.