Repository navigation
Stop calculating the location of _sysconfigdata for the WASI build script #144533
Description
Activity
- added 4 commits that reference this issue
on Feb 6, 2026 For posterity, I figured out why this approach was initially taken. The
_sysconfigdatamodule is found viagetpath.pywhich bases it on the location of the source checkout andpybuilddir.txt. Unfortunately, to get imports to work from a checkout we mount the checkout to/in the WASI guest which makes the checkout location recorded via./configurebe incorrect. As such, we need to usePYTHONPATHto manually include the build directory thatpybuilddir.txtpoints at. And since we need to setPYTHONPATHfor the host runner when we call./configureso it ends up inMakefile, we need to calculate the path to the build directory instead of getting to usepybuilddir.txt.Reacted by Jaime Andrés Gómez de Luna- changed the title
[-]Use `pybuilddir.txt` to find `_sysconfigdata` for the WASI build script[/-][+]Stop calculating the location of `_sysconfigdata` for the WASI build script[/+]on Feb 20, 2026 And Savannah has a better solution outlined in #144535 (comment) .
- added a commit that references this issue
on Feb 28, 2026
cpython/Platforms/WASI/__main__.py
Line 328 in 957f9fe
That should be reading the directory location from
pybuilddir.txtinstead.Linked PRs