-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
Emscripten support: Remove --with-emscripten-target
#126691
Labels
Comments
|
If this is possible, I agree it would be preferable. |
hoodmane
added a commit
to hoodmane/cpython
that referenced
this issue
Nov 13, 2024
This unifies the code for nodejs and the code for the browser. After this commit, the browser example doesn't work. However, I have a fix for it prepared as a followup.
freakboy3742
pushed a commit
that referenced
this issue
Nov 16, 2024
This unifies the code for nodejs and the code for the browser. After this commit, the browser example doesn't work; this will be fixed in a subsequent update.
picnixz
pushed a commit
to picnixz/cpython
that referenced
this issue
Dec 8, 2024
This unifies the code for nodejs and the code for the browser. After this commit, the browser example doesn't work; this will be fixed in a subsequent update.
ebonnal
pushed a commit
to ebonnal/cpython
that referenced
this issue
Jan 12, 2025
This unifies the code for nodejs and the code for the browser. After this commit, the browser example doesn't work; this will be fixed in a subsequent update.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


It's possible to support both node and the browser with a single configuration, for instance Pyodide does this. I think this is preferable since it's fewer options to have test coverage for or to not cover and be in doubt about whether they work. Requires refactoring the way the Python.html example and node runner work.
cc @freakboy3742
Linked PRs
The text was updated successfully, but these errors were encountered: