-
-
Notifications
You must be signed in to change notification settings - Fork 34.8k
[3.14] gh-151544: Fixes CVE-2026-12003 by removing the fallback to %VPATH%/Modules/Setup.local for discovering sources in getpath.py (GH-151545) #151565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
4d228c4
b76f1f9
b002dba
c5125ff
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| :file:`Modules/Setup.local` is no longer used as a landmark to discover | ||
| whether Python is running in a source tree, as it could potentially affect | ||
| actual installs. The :file:`pybuilddir.txt` file is now the sole indicator | ||
| of running in a source tree. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -368,6 +368,10 @@ def configure_wasi_python(context, working_dir): | |
| file.write(f'#!/bin/sh\nexec {host_runner} {python_wasm} "$@"\n') | ||
| exec_script.chmod(0o755) | ||
| log("🏃", f"Created {exec_script} (--host-runner)... ") | ||
| pybuilddir_txt = working_dir / "pybuilddir.txt" | ||
| if not pybuilddir_txt.exists(): | ||
| os.symlink(CHECKOUT / "pybuilddir.txt", pybuilddir_txt) | ||
| log("📝", f"Symlinked {pybuilddir_txt} to normal location") | ||
|
Comment on lines
+371
to
+374
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @savannahostrowski @brettcannon Without the
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
The wasmtime version isn't locked, so you should be able to update it (might need CLI updates because there was a change to the format at some point).
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Making this change (#151682) works, but I have no idea what the added effects may be, e.g. how easily can someone doing builds of 3.14 figure out that they need to update their wasmtime after the
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
So I say it's say to update the default host runner settings. |
||
| sys.stdout.flush() | ||
|
|
||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.