Skip to content

gh-5073: PEP 831: Clarify build backend flag propagation - #5074

Draft
pablogsal wants to merge 1 commit into
python:mainfrom
pablogsal:pep-831-build-details
Draft

gh-5073: PEP 831: Clarify build backend flag propagation#5074
pablogsal wants to merge 1 commit into
python:mainfrom
pablogsal:pep-831-build-details

Conversation

@pablogsal

Copy link
Copy Markdown
Member

No description provided.

@read-the-docs-community

Copy link
Copy Markdown

Documentation build overview

📚 pep-previews | 🛠️ Build #33905008 | 📁 Comparing f729d34 against latest (69a447a)

  🔍 Preview build  

2 files changed
± pep-0764/index.html
± pep-0831/index.html

Comment thread peps/pep-0831.rst
Comment on lines +566 to +567
Build Backend Guidance
----------------------

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In addition to guidance to build backends, should there be guidance for tools such as cibuildwheel which specify config to build backends?

For example, should they add an option to enable frame pointers in backends, and perhaps make it the default at some point?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants