remote: remote: Create a pull request for 'browser-python-runtime' on GitHub by visiting: remote: https://github.com/stirlingbridge/localfirst-demo/pull/new/browser-python-runtime remote: To github.com:stirlingbridge/localfirst-demo.git * [new branch] browser-python-runtime -> browser-python-runtime branch 'browser-python-runtime' set up to track 'origin/browser-python-runtime'.
gh pr create --title "Add browser-hosted Python CLI runtime using Pyodide/WASM" --body "$(cat <<'EOF' ## Summary - Implements a framework (`BrowserRuntime`) that lets a web app invoke Python CLI tools entirely in the browser via Pyodide/WASM, with an `exec()`-style API returning stdout/stderr/exitCode - Python execution runs in a Web Worker to keep the UI responsive; includes an `http_client` Python module that bridges HTTP requests through the browser's `XMLHttpRequest` to work around WASM networking limitations - Ships four demo commands (hello, sysinfo, fetch, files) and a terminal-style UI to exercise them ## Test plan - [ ] `npm install && npm run dev`, open http://localhost:5173 - [ ] Run `hello --name Test --shout` — should print `HELLO, TEST!` - [ ] Run `sysinfo` — should show Python version and platform info - [ ] Run `fetch https://httpbin.org/get` — should pretty-print JSON response - [ ] Run `files -r /tools` — should list the registered command scripts 🤖 Generated with [Claude Code](https://claude.com/claude-code) EOF )"
You're welcome! It was a fun one to build. When you're ready to pick it back up — whether that's the transparent HTTP support, fetching tools from GitHub, or anything else — just let me know.
First please open a new issue to cover the problems we found earlier with transparent url fetch. This will allow us to keep things straight when we come back to look into it further.
gh issue create --title "Support transparent HTTP patching for urllib/requests" --body "$(cat <<'EOF' ## Problem Python CLI tools running in the Pyodide/WASM environment cannot use standard HTTP libraries (`urllib.request`, `requests`) out of the box: - **HTTPS URLs** fail with `unknown url type: https` because the `ssl` module is not available in WASM - **HTTP URLs** fail with `Operation in progress` because raw sockets don't work in the WASM sandbox We attempted to use `pyodide-http` (which monkey-patches `urllib` and `requests` to route through browser `XMLHttpRequest`/`fetch`), but it failed silently. ## Current workaround We provide a custom `http_client` Python module that uses synchronous `XMLHttpRequest` via Pyodide's JS interop. CLI tools must explicitly `import http_client` instead of using `urllib` or `requests`. This works but means arbitrary Python tools that use standard HTTP libraries can't run unmodified. ## Goal Enable transparent HTTP support so that Python code using `urllib.request` or `requests` works without modification. Possible approaches: - Investigate why `pyodide-http` patching fails and fix it - Write our own monkey-patches for `urllib.request` handlers that delegate to `XMLHttpRequest` - Intercept at the socket level if Pyodide/Emscripten provides hooks for that - Track upstream Pyodide improvements to networking/SSL support ## Context - Pyodide v0.26.4 - Python runs in a Web Worker (synchronous XHR is available) - Only HTTP support is needed, not general-purpose networking EOF )"