Moving Data Logic to the Browser with PyScript
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.
Loading…
ReadMeFeed / Community knowledge
#pyodide
Real questions. Useful conversations. Find the people who know your stack.
pyscriptArchitectural note: Using PyScript's module loading and sandboxing for secure web apps
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.
Bridging Python and the DOM: Client-Side UI Logic with PyScript
Learn how to use PyScript to manipulate the HTML DOM using Python, enabling client-side logic without a backend server via Pyodide and WebAssembly.
Run reproducible browser Python with PyScript py-config package declarations
Run Python in the browser with reproducible dependencies by declaring packages in py-config before py-script execution. Covers prerequisites, config placement, validation checks, and recovery for missing Pyodide wheels.
Global state synchronization failure between JavaScript window and Python namespace
PyScript utilizes Pyodide to bridge the Python interpreter with the browser's JavaScript DOM API. A core requirement for complex web applications is the ability to maintain a consistent global state across both environments, specifically when modifying the JavaScript window object from within a PyScript execution block. While the runtime provides mechanisms
py-config initialization transition and concurrent request latency
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
wasmRepeated <py-env> additions cause steady WebAssembly memory growth in PyScript
When developing long‑running PyScript pages that dynamically insert and remove <py-env> blocks to load different packages, developers notice a gradual increase in the reported WebAssembly memory usage that does not drop after each removal. The goal is to ascertain whether this growth is an intended side‑effect of Pyodide’s module caching or a sign that
PyScript Next runtime configuration: Global namespace synchronization across backends
Runtime Configuration Transition PyScript Next (version 2023.11.1+) has transitioned to a decoupled configuration model using the <py-config> tag. This modular approach allows developers to switch between the Pyodide and MicroPython backends depending on the required footprint and library support. Namespace Synchronization Uncertainty While the <py-
PyScript Python ↔ JavaScript bridge: default global reachability of imported modules
PyScript runs Python in the browser via Pyodide and provides a JavaScript entry point that allows page scripts to invoke the Python runtime. Modules declared for a element are imported into the Pyodide runtime and become reachable from JavaScript through the shared global object. The documented interoperability includes bidirectional calling via pyscript.run