sphinx-contrib / sphinx-contrib/autoprogram
Use PEP 517 style build
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 48
- Forks
- 24
- Avg merge
- 2h 15m
- Merged PRs (30d)
- 1
Description
Many packages have switched to leverage PEP 517 style of building the package, dropping setuptools in the process.
At the same time, it may be worth considering changing setup.py into a more declarative pyproject.toml (or setup.cfg).
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 reviewing the existing setup.py and compare the PEP 517, pyproject.toml, and setup.cfg options named in the issue. Determine which declarative build configuration fits the package, then verify that the package still builds correctly; no test or other entry point is named.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100