-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Upgrade pyodide
compatibility to v0.24.1
#2402
Conversation
Failing the same way on my Mac laptop.
Coming from line 2 of CMakeLists.txt. Not sure why it's looking under |
the problem was pyodide/pyodide#4216 I was able to finish a build on my laptop, but it was a native .so for some reason. Building here while I debug locally, just in case it's a result of a quite dirty working tree. |
# PYTHON_VERSION and EMSCRIPTEN_VERSION are determined by PYODIDE_VERSION. | ||
# The appropriate versions can be found in the Pyodide repodata.json | ||
# "info" field, or in Makefile.envs: | ||
# https://github.com/pyodide/pyodide/blob/main/Makefile.envs#L2 | ||
PYTHON_VERSION: 3.11.2 | ||
EMSCRIPTEN_VERSION: 3.1.32 | ||
PYTHON_VERSION: 3.11.3 |
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.
this also changed? Is this durable to changes in setup-python
?
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.
ah meh # PYTHON_VERSION and EMSCRIPTEN_VERSION are determined by PYODIDE_VERSION.
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.
all gucci?
@@ -8,9 +8,6 @@ auto-save-list | |||
tramp | |||
.\#* | |||
|
|||
# npm lock file |
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.
unrelated change here --
I was rusty on perspective dev, used npm
by mistake instead of yarn and, without the "new untracked file" cue in git status
I didn't realize I had gone astray. Ended up with a busted node_modules directory from it
Of course we also don't want package-lock.json checked in. So I am happy to undo this, just wanted to raise the issue. Maybe there is a better way to help people like me avoid using npm in perspective dev
9349f9f
to
9b5cabe
Compare
includes a bump to Emscripten 3.1.45 and a workaround for a missing file upstream
9b5cabe
to
2d5bbff
Compare
pyodide
compatibility to v0.24.1
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.
Thanks for the PR! Looks good!
I want to spend more time understanding the emscripten
dependency of this build, specifically whether we are over-installing or over-building it.
No description provided.