wheelnext / wheelnext/variantlib
Ensure `variantlib` is vendorable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 0
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 4
Description
When working on the code in this repo, let's keep in mind that variantlib needs to be both reimplementable (e.g., in Rust) and vendorable (e.g., if a build frontend or backend cannot have dependencies, like pip).
I didn't audit all the code so this is just a single example - an absolute import like this won't work well, it breaks when variantlib is vendored:
from variantlib.loader import PluginLoader
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 with the shown from variantlib.loader import PluginLoader import and audit similar imports throughout the package. Determine the repository's requirements for reimplementability and vendoring, then verify that the package can be used when copied into a dependency-free build frontend or backend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100