ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #pyscript
A step‑by‑step guide to identify why PyScript fails to run Python code, with checks for script order, WASM MIME type, CORS, and CSP, plus fixes and escalation paths.
Learn how to use PyScript to move data manipulation logic from the backend to the browser using Pyodide and WebAssembly, reducing server overhead for data-heavy client tasks.
Architectural guide for using PyScript's <py-config> module loading and sandboxing to run isolated Python in the browser, with checks, failure modes, and design triggers.
Learn how to use PyScript to manipulate the HTML DOM using Python, enabling client-side logic without a backend server via Pyodide and WebAssembly.
PyScript runs Python in WebAssembly with a single-threaded event loop. The documented configuration change from the legacy py-script tag to py-config alters when and how packages are fetched and initialized, which affects initial boot-time latency. Under concurrent requests, the Micodide/Pyodide runtime still relies on a Global Interpreter Lock within a sing
Goal: ensure that external Python files referenced via the <py-script src> attribute are loaded only from the intended origin and that their source is not unintentionally exposed. Constraint: the src attribute relies on the browser's fetch mechanism and resolves relative URLs against the page's base URL, which can differ when the page is served from fi
Goal: Verify whether a network (or proposed allow‑network ) attribute on a <py-script> tag grants network access only to that specific script element or to all PyScript code on the page when testing third‑party API calls without production credentials. Uncertainty: The current documentation does not state if the permission is scoped per‑module or appli
wasm