Potentially. The PEP doesn’t make it clear who is going to be using it or when.
Does it need to be available for all installs? Only when people are compiling extensions?
Potentially. The PEP doesn’t make it clear who is going to be using it or when.
Does it need to be available for all installs? Only when people are compiling extensions?
I raised this with the steering committee in PEP 739 demands installation of the build-details.json name under the same name in the same location for different builds · Issue #341 · python/steering-council · GitHub. Currently I don’t know how to properly solve that with the layout used in Debian and Ubuntu.
It’s my understanding that this file isn’t yet used widely, but this will become a problem when this file needs to be installed for the standard build and the debug build at the same time for e.g. some package builds.