PEP 831: Clarify build backend flag propagation

Open Beginner friendly
#5,073 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
json, python
Domain
build-system, documentation

Research direction

Start by reading PEP 831 and the linked Python discussion, focusing on its claims about build flag propagation. Revise the PEP to distinguish Setuptools and deliberate sysconfig consumers from other PEP 517 backends, and document build-details.json as the future standardized interface. Done means these distinctions are stated accurately in the PEP.

Written by the indexing model from the issue text.

Description

PEP 831 currently overstates how CPython build flags propagate through generic build backends. Update the PEP to distinguish Setuptools and deliberate sysconfig consumers from other PEP 517 backends, and document build-details.json as the appropriate future standardized interface.

Context: https://discuss.python.org/t/pep-831-frame-pointers-everywhere-enabling-system-level-observability-for-python/106958/7

Dominant language
reStructuredText
Stars
5k
Forks
1.8k
Avg merge
2d 4h
Merged PRs (30d)
25

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/peps

All issues in python/peps

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.