Adding a wheel management API
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 751
- Forks
- 324
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 3
Description
I'm the maintainer of wheel. I'm wondering if you would be interested in receiving an API for reading and writing wheels in this project. I've been wondering for a while if it makes any sense for PyPA to have so many packaging projects.
This is what I had in mind:
- The new "wheel public API" would go into this project instead of
wheel setuptoolswould adopt this API and ditchwheelas a dependency for building wheelswheelwould depend onpackagingat run time (currently it vendors this project) and become nothing but a CLI tool- (optional)
auditwheelandwheelwould be merged (preferably intowheel) (optional, to be discussed later)
The goal is to get rid of at least one PyPA project.
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 by reviewing this issue's proposed relationship between packaging, wheel, setuptools, and auditwheel. Determine whether the project wants a wheel reading and writing API and define the scope and ownership of that API before identifying implementation files or tests; done would require agreement on the design and project boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100