ydb-platform / ydb-platform/ydb-python-sdk
dev: Refactor legacy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 102
- Forks
- 75
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100