ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #pyscript
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.
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.
A <py-script> that performs CPU-bound work or awaits a slow operation cannot be interrupted uniformly. When execution runs on the browser main thread, a synchronous Python loop freezes the page, and no documented timeout attribute on the tag reliably stops it. Moving execution into a Web Worker via the worker attribute or <py-worker> keeps the UI
Symptom When the <py-env> tag is updated to request a newer version of a pure‑Python wheel, subsequent <py-script> blocks sometimes fail with ModuleNotFoundError or continue to use the old cached version. Goal Determine a reliable pattern that lets a small browser‑based application load a new package version without a full page reload while guara
Goal Migrate a small client-side Python web app to a newer PyScript release without downtime, using only static file changes and browser cache control. Constraint PyScript loads Pyodide core through its loader script. If those core files cannot be fetched, existing py-script blocks stay inert and the page renders without Python execution. Because execution h
PyScript exposes two distinct execution surfaces: the main-thread <py-script> tag and the isolated <py-worker> context. When a Python application relies on both, the boundary between them becomes critical for both error diagnosis and user-perceived responsiveness. A documented behavior is that Pyodide exceptions are translated into JavaScript exc
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
PyScript Component Lifecycle The goal is to manage UI state consistency following a conceptual data model change, not database rollback. Constraint Uncertainty PyScript's declarative component structure offers predictable rendering, but runtime state management within the browser context lacks built-in schema versioning. Should state persistence rely solely