-
Notifications
You must be signed in to change notification settings - Fork 40
Update to pyodide 0.28.1, micropip 0.10 #202
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
Conversation
@@ -560,7 +559,7 @@ ${e.stack}`; | |||
reject: () => void; | |||
resolve: () => void; | |||
} | null = null; | |||
protected _pyodide: Pyodide.PyodideInterface = null as any; | |||
protected _pyodide: Pyodide.PyodideAPI = null as any; |
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.
Noting that PyodideInterface
can be brought back when upgrading to 0.28.2: pyodide/pyodide#5827
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.
I'm not sure if we should go ahead with this PR since the latest pyodide 0.28.1 dropped a couple of packages due to build issues.
So maybe we should not backport that as a 0.6.x change because this is likely going to break some deployments.
@agriyakhetarpal what do you think about opening a new PR against main
to update to the 0.28.2 version? Thanks!
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.
You're right; we've been working to build back the most commonly requested packages in pyodide/pyodide-recipes#99. It will take a bit of time until this is ironed out, because it is something we have to take up with the maintainers of those disabled packages and we cannot bring them back alone.
A new PR to update to Pyodide 0.28.2 makes sense to me, I'll create one!
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.
Yep, "don't break user space," is a good reason to belay this, will close out.
references
@jupyterlite/kernel
assets are needed innode_modules
(not justsharedPackages
) to be built into the workersmicropip
stuff, but this is not sustainablechanges
pyodide 0.28.1
in the usual placespyodide.PyodideInterface
topyodide.PyodideAPI
piplite
formicropip 0.10.1
--reinstall
and--constraints
backwards incompatible changes
python 3.13
andemscripten 4
0.7.x
line, even if0.6,x
(which would stay onpyodide 0.27
) continues to get updates for the nextjupyterlite-core
alternatives