-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
gh-127503 Don't propagate native PATH to Emscripten Python #127633
gh-127503 Don't propagate native PATH to Emscripten Python #127633
Conversation
This makes `shutil.which()` pick up native executables which is inconvenient.
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 |
I think the problem was introduced in the web_example PR here: The issue is that |
Opened #127666 with a fix. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 With the fix from #127666, I can now confirm this works as expected.
The native PATH makes
shutil.which()
pick up native executables which is inconvenient.While I'm at it, I also set
thisProgram
incorrectly in the final version of #127506.