Explore migration tooling
Open
Nobody has claimed this yet.
feature
- Dominant language
- Rust
- Stars
- 20
- Forks
- 0
- Avg merge
- 4m
- Merged PRs (30d)
- 8
Description
Should we support a migrate subcommand?
Some things to look into:
- Convert setup.cfg metadata -> [project] table
- Normalize dependency lists to PEP 508 conventions
- Convert dev/test tool configs to standardized [tool.*] sections
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
No files, tests, or entry points are named. First map the existing command and configuration-parsing paths, then define expected conversions for setup.cfg metadata, PEP 508 dependencies, and dev/test [tool.*] sections; done requires an agreed scope and coverage for each conversion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100