ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #pyscript
Learn how to solve PyScript's 'cold start' problem by optimizing module loading and using direct DOM interaction for responsive, browser-based Python apps.
Learn how to use the <py-config> tag in PyScript to manage Python dependencies and local modules for client-side execution via WebAssembly.
Learn how PyScript’s <py-env> tag declaratively installs Python packages via Pyodide, where the dependencies are cached in IndexedDB, and what to check when things go wrong.
PyScript imports fail when packages are missing from py-config. Learn how the packages list controls both correctness and page load cost, with a minimal example and verification steps.
Learn how to architect client-side Python applications using PyScript and Pyodide, including Wasm runtime boundaries, DOM interop, and critical performance limitations.
Learn how to bridge the gap between Python logic and the browser DOM using PyScript and Pyodide's FFI to create interactive, data-driven web interfaces.
Learn how to import external Python packages in Pyscript using the <code>pip</code> directive. The guide explains the mechanism, shows a worked example, and covers limits and common pitfalls.
Declare Python dependencies in a <py-config> block so PyScript loads them via Pyodide and micropip before any <py-script> runs. This enables browser-only demos with pure-Python packages while trading load size and memory for serverless execution.
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.