Feature or enhancement

Proposal:

ingetpath.c, the generated frozengetpath.h is [included using relative path](

I'd like to consider changing this touse absolute include path.
my primary motivation is to make it possible to build python using alternative build systems (buck2 in my case), where frozen modules are generated as intermediate build artifacts, and it's not straight forward (read: I couldn't figure it out yet) to make the generated header "look like" it's in that relative path.

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

Linked PRs

• gh-113039: Don't use relative include path in getpath.c #113022