dev: Refactor legacy

Open
#884 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
api

Research direction

Start with the linked inheritance example in ydb/table.py around line 89, then inspect nearby Python 2 patterns and typing imports. Confirm the intended refactoring scope before changing files; done means the agreed legacy patterns are removed while Python 3.10+ compatibility is preserved and the project tests pass.

Written by the indexing model from the issue text.

Description

enhancement

Our codebase still contains legacy Python 2 patterns, even though Python 2 is now end-of-life. For instance, explicit inheritance from object is redundant in Python 3. Also, while we could replace typing imports (e.g., List, Dict) with built-in generics (list, dict) since we're on Python 3.9+. Project already requires Python 3.10+. What do you think about a small refactoring? I’d like to work on it.

Dominant language
Python
Stars
102
Forks
75
Avg merge
1d 23h
Merged PRs (30d)
13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ydb-platform/ydb-python-sdk

All issues in ydb-platform/ydb-python-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.