apache/gravitino

[Improvement] Fix client-python codes to conform Pylint Rules

Open

#3,560 opened on May 25, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (887 forks)auto 404
good first issueimprovement

Repository metrics

Stars
 (3,058 stars)
PR merge metrics
 (PR metrics pending)

Description

What would you like to be improved?

There are some Pylint Rules that were disabled now (labeled by TODO-fix in pylintrc) but needed to be fixed to conform the Pylint standards.

  • missing-timeout #3765
  • redefined-builtin: #3561
  • broad-exception-caught #3766
  • duplicate-code #3767
  • method-hidden #3768
  • invalid-field-call #3769
  • protected-access #3770
  • too-many-arguments
  • no-name-in-module #3771
  • inconsistent-return-statements #3771

How should we improve?

No response

Contributor guide

Research direction
Address the remaining pylint issues by fixing missing timeout, broad exception caught, duplicate code, and too many arguments in the Python client code. Refer to existing fixed issues for patterns.
Tech stack
python
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Pythonpylint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75