FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

gh-5073: PEP 831: Clarify build backend flag propagation by pablogsal · Pull Request #5074 · python/peps · GitHub

/ peps Public

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

Copy link
Copy Markdown
Member

No description provided.

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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

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?

savannahostrowski left a comment
edited
Loading

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.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

The clarification here looks right to me. I left a comment on python/cpython#155172; depending on the intended scope there, we may want to reflect its relationship to the future standardized field here.

We'll probably also want to update corresponding CPython docs, since Doc/using/configure.rst still says that the flags "propagate to third-party C extensions through sysconfig".

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
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.

3 participants


Back | FazBrowse Home | New Git URL