Scikit-build (classic) 1.0 internals
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1k
- Avg merge
- 22h 17m
- Merged PRs (30d)
- 3
Description
Hi,
I'm currently working on swapping out scikit-build (classic)'s internals for scikit-build-core, and I have AI running lots of downstream projects and looking for regressions. It found that this project currently uses scikit-build internals. I've been able to patch some of them back in as shims, but opencv-python fiddles with stuff like skbuild.setuptools_wrap._classify_installed_files that's simply not there anymore.
See https://github.com/scikit-build/scikit-build/pull/1185. I can try to propose something here if you'd like. The best thing would be to use scikit-build-core without setuptools directly.
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 the scikit-build (classic) to scikit-build-core migration described in scikit-build/scikit-build#1185. Search this project for uses of skbuild.setuptools_wrap._classify_installed_files and other scikit-build internals, then check downstream projects for regressions. Done means the package uses scikit-build-core without setuptools directly and those downstream builds continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100