Skip to content

Prepare release 1.0.0 (Pyodide → Emscripten breaking rename)#201

Open
FeodorFitsner wants to merge 2 commits into
mainfrom
pyodide-to-emscripten
Open

Prepare release 1.0.0 (Pyodide → Emscripten breaking rename)#201
FeodorFitsner wants to merge 2 commits into
mainfrom
pyodide-to-emscripten

Conversation

@FeodorFitsner
Copy link
Copy Markdown
Contributor

Summary

  • Rename the --platform argument value Pyodide to Emscripten so it matches what platform.system() returns inside the Pyodide runtime, keeping PEP 508 markers like platform_system != 'Emscripten' consistent across build-time and in-browser micropip paths.
  • Bump all packages (serious_python and the 5 platform packages, podspec, Android build.gradle) to 1.0.0 and refresh example app pubspec.lock files.
  • Add a 1.0.0 entry to all six CHANGELOG.md files marking the rename as a breaking change.

Test plan

  • CI green on the branch
  • Verify package command with --platform Emscripten produces the expected web build
  • Confirm PEP 508 markers platform_system != 'Emscripten' resolve correctly during pip resolution

🤖 Generated with Claude Code

FeodorFitsner and others added 2 commits May 11, 2026 12:33
The sitecustomize.py injected at pip-resolution time monkey-patches
`platform.system()` to the platform argument value. Renaming `Pyodide` to
`Emscripten` aligns that value with what `platform.system()` actually returns
in a real Pyodide runtime, so PEP 508 markers like `platform_system != 'Emscripten'`
work consistently in both the build-time and in-browser micropip paths.
Bump all packages to 1.0.0 and add changelog entries marking the
Pyodide → Emscripten platform argument rename as a breaking change.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant