gh-144533: Use pybuilddir.txt to find _sysconfigdata for WASI #144535
Conversation
therohityadav
requested review from
brettcannon,
emmatyping and
savannahostrowski
as code owners
|
All commit authors signed the Contributor License Agreement. |
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the |
therohityadav
force-pushed
the
fix-wasi-build-144533
branch
2 times, most recently
from
035c77e to
b64935a
Compare
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Platforms/WASI/__main__.py
Outdated
| with pybuilddir.open("r", encoding="utf-8") as f: | ||
| sysconfig_data_dir = f"{wasi_build_dir}/{f.read().strip()}" | ||
| else: | ||
| # Fallback if the build hasn't generated the file yet |
There was a problem hiding this comment.
Something feels off. Why did I ever care about setting this when configuring the host? If I remember correctly it was because tests failed using the host runner if I didn't via make test. But that doesn't seem right since that would mean a WASI build was somehow special in regards to paths compared to any other build which it shouldn't be. Plus if the python.sh shell script works which doesn't make the change to PYTHONPATH then it really feels weird that this is even here.
Can someone test what happens if you just take out the environment updates?
There was a problem hiding this comment.
Yeah, that's right. I tested removing the environment updates. Without PYTHONPATH, tests fail with ModuleNotFoundError: No module named '_sysconfigdata__wasi_wasm32-wasi' (because this lives in the build dir and not in Lib/, I think).
python.sh does include PYTHONPATH. It's just passed in via --env in the wasmtime command.
There was a problem hiding this comment.
Is this an out-of-tree build issue? I never bothered to figure out why this is an issue since you would think all builds have the same situation and yet none of us set it when we run the test suite from a checkout.
therohityadav
force-pushed
the
fix-wasi-build-144533
branch
from
b64935a to
0ecc19e
Compare
3 participants
pybuilddir.txtto find_sysconfigdatafor the WASI build script #144533Use
pybuilddir.txtto find_sysconfigdatafor the WASI build script.The previous implementation hardcoded the path pattern to
build/lib.wasi-wasm32-{python_version}. This change makes the script more robust by reading the exact build directory frompybuilddir.txtif it exists. It falls back to the hardcoded path if the file is missing to ensure backward compatibility during early build stages.