Uh oh!
There was an error while loading. Please reload this page.
gh-127503 Don't propagate native PATH to Emscripten Python - #127633
Conversation
This makes `shutil.which()` pick up native executables which is inconvenient.
freakboy3742
commented
Dec 6, 2024
I thinks this change makes sense; however, in trying to test it, I've hit an issue. I don't think the problem is related to this change specifically; I can't tell if it's related to #127506, or if I've done something to my EMSDK config. I suspect it's manifesting now because I had to do a complete rebuild of both the host and build Python, whereas during my testing of #127506 I had a pre-existing build, and I was only testing the script updates. The problem manifests as an error during Any ideas where that could be coming from? It looks like it's a misconfiguration of the |
hoodmane
commented
Dec 6, 2024
I think the problem was introduced in the web_example PR here: The issue is that |
hoodmane
commented
Dec 6, 2024
Opened #127666 with a fix. |
freakboy3742
left a comment
There was a problem hiding this comment.
👍 With the fix from #127666, I can now confirm this works as expected.
…hon#127633) Modifies the handling of PATH to ensure that native executables aren't picked up when running under node.
The native PATH makes
shutil.which()pick up native executables which is inconvenient.While I'm at it, I also set
thisProgramincorrectly in the final version of #127506.