Making Your Documentation Interactive with PyScript
summary
Claim: documentation examples become runnable in the browser with no backend or installation by embedding PyScript (CPython via Pyodide) into pages. Tooling integrates with Sphinx and MkDocs, deploys to GitHub Pages or readthedocs, and installs packages from PyPI, the pyodide repo, or wheel URLs. Pages use interactive code cell editors, setup tags and shared environment options to share interpreter state. Worker threads and SharedArrayBuffer require secure contexts. Works for pure‑Python and many scientific packages; limitations include threading, native GUI and raw sockets.
AI-written summary · about
chapters (13)
- 0:00Interactive docs with PyScript
- 1:04Problem with static examples
- 3:11What we’ll cover
- 3:53Jeff Glass and PyScript
- 5:40PyScript runs Python in browser
- 7:46PyScript editor cells concepts
- 13:46Editor cell config tags
- 14:52PyScript with Sphinx/MkDocs
- 19:03Deploying PyScript docs
- 22:36Secure contexts and buffers
- 24:20PyScript: what works vs what doesn’t
- 27:05PyScript resources
- 28:08Q&A
related talks
39mBuild Yourself a PyScript
32mPyScript - what you need to know
44mRethinking Data Visulisation with PyScript
39mPyScript - Python in the Browser
30mNext Level Python Applications with PyScript
29mPyscript for Education
42mPyScript & Data Science- PyData stack on the Browser
29mPyScript and Data Science: a love story