PyScript
framework for running Python scripts in a web browser
PyScript is a framework for running Python scripts in a web browser. PyScript was presented to the public by Peter Wang at a Python developer conference in June 2022. PyScript is primarily developed by Anaconda, Inc.
Usage
PyScript allows Python scripts, which normally run on a server, to be executed in a web browser. This allows the same programming language to be used in the backend (on the server) and in the frontend (in the web browser). PyScript is a TypeScript library that is loaded by the web page and interprets the embedded Python scripts. Apart from PyScript's JavaScript library and CSS rules, there are no other dependencies. JavaScript is typically used to provide dynamic functionality to a web page. PyScript can replace JavaScript, but it can also run side-by-side with JavaScript. This allows JavaScript to call PyScript functions and vice versa.
The public source identifies “PyScript” as framework for running Python scripts in a web browser. This brief keeps that definition visible, then builds a research path around PyScript, framework and running.
Why this record matters
A short description can identify a subject without explaining its stakes. For “PyScript”, the useful work is to connect “framework for running Python scripts in a web browser” to the records capable of establishing context and consequence.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Aug 27, 2026. The linked authority identifier is Q115750242. 1 of 2 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 2022.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “PyScript”, its source revision and the description used here.
- Expand the search: follow PyScript primary sources, PyScript archive and PyScript research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “PyScript”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “PyScript” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.