PythonCharmers/python-future

Provide more granular codemods

Open

#440 opened on Mar 13, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (1,172 stars) (327 forks)batch import
0.20enhancementhelp wanted

Description

For large codebases, it's helpful to have minimally small codemods, to reduce the volume of change associated with each commit.

There are some fixers (i.e. builtins, itertools) that might benefit from being split up.

Contributor guide

Tech stack
python
Domain
toolingdeveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Python 2/3 compatibility knowledgebasic understanding of codemods
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Start by examining the existing codemods in the repository, particularly the 'builtins' and 'itertools' fixers. Understand how they are structured and how they transform code. Then, consider how to split these fixers into smaller, more targeted codemods. Look at any related discussions or PRs for prior attempts. The maintainers may have specific preferences for how the split should be done, so consider opening a discussion to clarify the scope.