Skip to content

gh-131372: Configurable build-details.json name - #150098

Merged
FFY00 merged 3 commits into
python:mainfrom
stefanor:build-detials-name
May 25, 2026
Merged

gh-131372: Configurable build-details.json name#150098
FFY00 merged 3 commits into
python:mainfrom
stefanor:build-detials-name

Conversation

@stefanor

@stefanorstefanor commented May 19, 2026

Copy link
Copy Markdown
Contributor

Linux distributions that co-install multiple Python versions in the same path (e.g. multiarch on Debian, debug builds, and free-threading) need a way to place multiple build-details.jsons side-by-side.

PEP-739 is being updated to recommend renaming in this situation. To ensure some standardisation, this PR generates appropriate names for distributions that need to use this feature. The name will be exposed in sysconfig.

My first preference would be to always do this, using the ABIFLAGS directly in the name. But this leads to less-human-readable names and the PEP authors preferred a static name where possible and a more verbose name, when we choose to rename.

@FFY00

@FFY00

Copy link
Copy Markdown
Member

I would prefer to rename the configure option to something like --with-build-details-identifier, working similarly to --with-build-python. If the option wasn't passed, no identifier is added, if it is passed without value, it would default to $MULTIARCH$threading_suffix$debug_suffix, and if it is passed with a value, the specified value would be used.

What do you think?

@stefanor

Copy link
Copy Markdown
ContributorAuthor

That works for me!

@stefanor
stefanorforce-pushed the build-detials-name branch from b6759d2 to 1345552CompareMay 19, 2026 19:19
Linux distributions that co-install multiple Python versions in the same
path (e.g. multiarch on Debian, debug builds, and free-threading) need a
way to place multiple build-details.jsons side-by-side.
PEP-739 is being updated [0] to recommend renaming in this situation. To
ensure some standardization, this PR generates appropriate names for
distributions that need to use this feature.
[0]: python/peps#4889
@stefanor
stefanorforce-pushed the build-detials-name branch from 1345552 to adb7586CompareMay 19, 2026 19:21
@stefanor

Copy link
Copy Markdown
ContributorAuthor

@FFY00: Implemented that

@picnixz

Copy link
Copy Markdown
Member

Can we have an issue for those kind of changes? this is solely so that people can more easily report issues later and for cross-references (or use an existing one)

@stefanorstefanor changed the title Configurable build-details.json nameGH-131372 Configurable build-details.json nameMay 20, 2026
@stefanor

Copy link
Copy Markdown
ContributorAuthor

Can we have an issue for those kind of changes? this is solely so that people can more easily report issues later and for cross-references (or use an existing one)

Ah, there was already an issue, I'd forgotten about it.

@stefanor
stefanorforce-pushed the build-detials-name branch from a606e8b to 900ec0dCompareMay 20, 2026 15:10
@picnixzpicnixz changed the title GH-131372 Configurable build-details.json namegh-131372: Configurable build-details.json nameMay 20, 2026
Comment threadconfigure.ac
Comment threadMisc/NEWS.d/next/Build/2026-05-19-12-45-23.gh-issue-131372.oJykeB.rst Outdated
@read-the-docs-community

Copy link
Copy Markdown

Documentation build overview

📚 cpython-previews | 🛠️ Build #32802775 | 📁 Comparing 078b7bb against main (3c298e2)

🔍 Preview build

3 files changed
±using/configure.html
±whatsnew/3.16.html
±whatsnew/changelog.html

@FFY00FFY00 left a comment

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.

Thanks @stefanor 😊

With the new changes, the PR looks great!

@FFY00
FFY00 merged commit 9c23f34 into python:mainMay 25, 2026
54 checks passed
@stefanor
stefanor deleted the build-detials-name branch May 25, 2026 14:06
Comment threadconfigure.ac
[
AC_MSG_CHECKING([for --with-build-details-suffix])
AS_VAR_IF(
[with_build_detials_suffix], [no],

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Shouldn't this have been...

Suggested change
[with_build_detials_suffix], [no],
[with_build_details_suffix], [no],

... instead?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

Ooh, thanks!

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

You can see the same typo in the branch name :)

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

@stefanorstefanor mentioned this pull request May 25, 2026
Sign up for freeto 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.

5 participants

@stefanor@FFY00@picnixz@vstinner@KowalskiThomas