PEP 739 demands installation of the build-details.json name under the same name in the same location for different builds

[doko42]

Seen with 3.14.x:

PEP 739 demands installation of the build-details.json name under the same name in the same location for different builds. This is a problem for the Debian and Ubuntu Python builds. These are installed under the same prefix, and share the same file hierarchy. Everything else in this tree can be differentiated by names, like extension suffixes, config-* directory names, sysconfig_data_.py and sysconfig_vars_.json files.

I am aware that the PEP describes installation of this file under a different name in a different name, however that still leaves the file conflict for these two installations.

I currently cannot see, how to make the Debian and Ubuntu builds conforming to PEP 739. Any ideas how to address this with a common prefix for both builds would be appreciated.

[JelleZijlstra]

Have you posted about this issue on discuss.python.org ? It's better to try to find a solution in open discussion before going to the Steering Council.

[merwok]

Yes this has been ongoing: https://discuss.python.org/t/pep-739-static-description-file-for-build-details-of-python-installations/44572/98

[FFY00]

I have discussed this issue with Stefano, and my preferred solution would be to add some text to the PEP specifying that in case of conflicts with other installations, a unique extension should be added to the file, eg. build-details.some-variant.json. This seemed to be good enough for Debian, as far as I understood.