Skip to content

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

Closed
wants to merge 7 commits into from

Conversation

bollwyvl
Copy link
Contributor

@bollwyvl bollwyvl commented Aug 3, 2025

references

changes

  • use pyodide 0.28.1 in the usual places
  • update reference from pyodide.PyodideInterface to pyodide.PyodideAPI
  • update piplite for micropip 0.10.1
    • add CLI args --reinstall and --constraints
    • ???

backwards incompatible changes

  • bumps to python 3.13 and emscripten 4
    • as discussed in a couple places, this seems big enough to warrant starting an 0.7.x line, even if 0.6,x (which would stay on pyodide 0.27) continues to get updates for the next jupyterlite-core

alternatives

  • make changes on 0.6.x
    • might well break folk that have custom wheels

Copy link
Contributor

github-actions bot commented Aug 3, 2025

lite-badge 👈 Try it on ReadTheDocs

@bollwyvl bollwyvl changed the title Update to pyodide 0.28, micropip 0.10 Update to pyodide 0.28.1, micropip 0.10 Aug 5, 2025
@bollwyvl bollwyvl added the enhancement New feature or request label Aug 5, 2025
@bollwyvl bollwyvl changed the base branch from main to 0.6.x August 6, 2025 13:39
@@ -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;
Copy link
Member

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

Copy link
Member

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!

Copy link
Member

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!

Copy link
Contributor Author

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.

@bollwyvl bollwyvl closed this Aug 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support pyodide 0.28.0
3 participants