pypa / pypa/packaging.python.org
Maintaining the example build backend specifiers
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 1.7k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 4
Description
Issue Description
In #1880, questions were raised regarding the maintainability of the example build backend dependencies. Specifically:
- how to handle backends that recommend upper bounds on the backend version (while tools that create per-package build environments can handle those without issue, they are a potential problem for build systems that aim to create unified build environments, such as those for Linux distros and from-source stack building projects like fromager)
- how to ensure we're not recommending excessively outdated versions of the backends
Some flavour of automation could help with the latter problem, but the former problem is a trickier one.
Code of Conduct
- I am aware that participants in this repository must follow the PSF Code of Conduct.
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
Read the “Declaring the build backend” guide section and the linked #1880 discussion first. Compare the documented backend specifiers with the two maintenance concerns in this issue; done requires a decided, maintainable approach for version bounds and avoiding excessively outdated backend versions, reflected in the example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100