Skip to content

Move the browser runtime to Pyodide 3.15 when it ships #74

Description

@tamnd

Pyodide ships CPython 3.14. The pin is 3.15. Everything about handling that gap is built and documented, and #2 is closed on it: cells that differ carry a note, nbversion compare checks the notes against what the two interpreters actually printed, and the versions job in CI is gating.

What is left is not ours to schedule. When Pyodide ships 3.15 the widgets and the WASM islands should move to it, and most of the notes in the lessons stop being needed.

The work

  • Watch for a Pyodide release built on CPython 3.15
  • Bump the runtime the widgets and the site islands load
  • Re-run just versions against the new pair and delete the notes that have become stale, which the check will name for us
  • Update the "which Python is this" paragraph in every lesson that has one

Why this is cheap when it happens

nbversion compare fails on a note whose cell no longer differs, so the day the runtime moves the check produces the exact list of paragraphs to delete. That was the argument for building the stale half of it rather than only the undeclared half.

Nothing blocks on this. The lessons are correct on both versions today, which is the point of the notes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/siteThe book site, WASM export, hosting and accessibilitykind/choreBuild, CI, dependencies and repository plumbingpriority/p2Wanted, not scheduledstatus/blockedWaiting on another issue

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions