ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
PyScript lets you run Python in the browser, but large runtimes, main-thread blocking, and client-side trust issues require deliberate architecture. Choose the smallest runtime, offload compute to a Web Worker, and keep secrets on the server.
A decision guide for picking Pyodide or MicroPython in PyScript: compare bundle size, startup time, package availability, threading, and JavaScript interop. Includes minimal working HTML for each runtime and a validation checklist using browser DevTools.
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
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-
Goal: Determine whether Python global state remains consistent when switching between the Pyodide and MicroPython runtimes within a single PyScript Next page. Constraints: The runtime selection is defined in a py-config JSON block; switching requires either re‑loading the block or dynamically inserting a new script type=\"py\" tag with a different runtime sp
pyscript