python-pillow / python-pillow/Pillow
Move custom build in setup.py to custom backend in _custom_build
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13.8k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 89
Description
Do we need to deprecate setup.py at some point or can it continue to exist indefinitely? Is there any tangible benefit, security or otherwise to move C extension builds to pyproject.toml? Can we assume we'd use the what's the expected level of effort? I saw #9642 and it made me curious about it.setuptools backend and
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 setup.py, pyproject.toml, and the custom build discussion in issue #9642. Compare the current C extension build arrangement with the proposed custom backend in _custom_build, then document whether setup.py should be deprecated, any tangible security or other benefits, and the expected effort.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100