RFC: Changes for version 2.0
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14
- Forks
- 4
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 1
Description
We're working on moving most of the implementation into packaging.dependency_groups, and pip install --group is now available.
I think I'd like to wait until packaging.dependency_groups has been out for a while, and then make the following changes:
- depend on
packaginginstead of the implementation here- slim down the tests
- update the main entry point (which prints groups) and the lint entry point to use the new implementation
- remove the pip wrapper -- people can use newer
pipversions - release the resulting, smaller, package as 2.0
I think that's all; it looks pretty straightforward to me.
I'm curious if anyone has feedback about this plan.
Contributor guide
No contributing guide indexed for this repository
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 by reading packaging.dependency_groups and PR 1065, then inspect the current main entry point that prints groups and the lint entry point. Done means depending on packaging, slimming the tests, removing the pip wrapper, updating both entry points, and preparing the smaller package for a 2.0 release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100