GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — gh-136267: Use the target configuration in build-details.json by itamaro · Pull Request #161529 · python/cpython

Conversation

@itamaro

@itamaro itamaro commented Nov 7, 2026 •
edited by bedevere-app Bot
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

With --with-build-python, generate-build-details.py runs on an interpreter other than the one being built. abi.flags, suffixes.extensions, abi.stable_abi_suffix and supports_isolated_interpreters came from sys and importlib, so they described the build interpreter. This reads them from sysconfig instead. The suffix list is rebuilt the way dynload_shlib.c builds it, and a test checks the result against importlib.machinery.EXTENSION_SUFFIXES on native builds.

Also sets abi.extension_suffix and abi.stable_abi_suffix for static libpython builds. PEP 739 requires them whenever extension modules are supported; they were only emitted with a shared libpython (rust-cross/manylinux-cross#165).

Tested with ./configure --disable-gil --with-build-python=<GIL-enabled debug python> && make build-details.json: the file now has ["t"] and the free-threaded suffix list instead of the build interpreter's ["d"] and its list.

Written with assistance from Claude Fable 5.1

  • Issue: PEP-739 build-details generation is incorrect when cross-building #136267

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@itamaro @claude
pythongh-136267: Use the target configuration in build-details.json
1849e72
With --with-build-python, generate-build-details.py runs on a different
interpreter than the one being built. abi.flags, suffixes.extensions,
abi.stable_abi_suffix and supports_isolated_interpreters came from sys and
importlib, so they described the build interpreter. Read them from
sysconfig instead. The extension suffix list is rebuilt the same way
Python/dynload_shlib.c builds it; a test checks that the result matches
importlib.machinery.EXTENSION_SUFFIXES on native builds.

Also set abi.extension_suffix and abi.stable_abi_suffix for static
libpython builds. They were only set with a shared libpython, but
extension modules work either way and PEP 739 requires them.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
@itamaro
itamaro requested a review from brettcannon November 7, 2026 04:33
@itamaro itamaro added build The build process and cross-build needs backport to 3.14 bugs and security fixes needs backport to 3.15 bugs and security fixes labels Nov 7, 2026
@bedevere-app bedevere-app Bot mentioned this pull request Nov 7, 2026
PEP-739 build-details generation is incorrect when cross-building #136267
Open
@itamaro
itamaro marked this pull request as ready for review November 7, 2026 06:07
@itamaro
itamaro requested a review from FFY00 as a code owner November 7, 2026 06:07
@bedevere-app bedevere-app Bot added the awaiting core review label Nov 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@brettcannon brettcannon Awaiting requested review from brettcannon
@FFY00 FFY00 Awaiting requested review from FFY00 FFY00 is a code owner

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

awaiting core review build The build process and cross-build needs backport to 3.14 bugs and security fixes needs backport to 3.15 bugs and security fixes

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@itamaro
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.