Use latest instead

Fix 404 in main README.md
use UTC time (#1859 )
2025-12-19 18:27:29 -05:00 · 2023-11-21 11:11:57 -06:00 · 2023-11-21 11:09:48 -06:00 · 2023-11-15 16:00:09 +01:00 · 2023-11-15 12:10:52 +01:00 · 2023-11-14 15:25:17 +01:00
4 changed files with 77 additions and 8 deletions
--- a/README.md
+++ b/README.md
@@ -4,9 +4,9 @@

 ### Summary

-PyScript is a framework that allows users to create rich Python applications in the browser using HTML's interface and the power of [Pyodide](https://pyodide.org/en/stable/), [WASM](https://webassembly.org/), and modern web technologies.
+PyScript is a framework that allows users to create rich Python applications in the browser using HTML's interface and the power of [Pyodide](https://pyodide.org/en/stable/), [MicroPython](https://micropython.org/) and [WASM](https://webassembly.org/), and modern web technologies.

-To get started see the [getting started tutorial](docs/tutorials/getting-started.md).
+To get started see the [getting started tutorial](https://pyscript.github.io/docs/latest/beginning-pyscript/).

 For examples see [here](examples).

@@ -16,7 +16,7 @@ PyScript is a meta project that aims to combine multiple open technologies into

 ## Try PyScript

-To try PyScript, import the appropriate pyscript files into the `<head>` tag of your html page with:
+To try PyScript, import the appropriate pyscript files into the `<head>` tag of your html page:

 ```html
 <head>
@@ -29,14 +29,25 @@ To try PyScript, import the appropriate pyscript files into the `<head>` tag of
        src="https://pyscript.net/releases/2023.11.1/core.js"
    ></script>
 </head>
+<body>
+    <script type="py" terminal>
+        from pyscript import display
+        display("Hello World!") # this goes to the DOM
+        print("Hello terminal") # this goes to the terminal
+    </script>
+</body>
 ```

-You can then use PyScript components in your html page. PyScript currently implements the following elements:
+You can then use PyScript components in your html page. PyScript currently offers various ways of running Python code:

-   `<py-script>`: can be used to define python code that is executable within the web page. The element itself is not rendered to the page and is only used to add logic
-   `<py-repl>`: creates a REPL component that is rendered to the page as a code editor and allows users to write executable code
+-   `<script type="py">`: can be used to define python code that is executable within the web page.
+-   `<script type="py" src="hello.py">`: same as above, but the python source is fetched from the given URL.
+-   `<script type="py" terminal>`: same as above, but also creates a terminal where to display stdout and stderr (e.g., the output of `print()`); `input()` does not work.
+-   `<script type="py" terminal worker>`: run Python inside a web worker: the terminal if fully functional and `input()` works.
+-   `<py-script>`: same as `<script type="py">`, but it is not recommended because if the code contains HTML tags, they could be parsed wrongly.
+-   `<script type="mpy">`: same as above but use MicroPython instead of Python.

-Check out the [the examples directory](examples) folder for more examples on how to use it, all you need to do is open them in Chrome.
+Check out the [official docs](https://docs.pyscript.net) for more detailed documentation.

 ## How to Contribute

@@ -44,6 +55,17 @@ Read the [contributing guide](CONTRIBUTING.md) to learn about our development pr

 Check out the [developing process](https://docs.pyscript.net/latest/contributing) documentation for more information on how to setup your development environment.

+## Community calls and events
+
+Every Tuesday at 15:30 UTC there is the _PyScript Community Call_ on zoom, where we can talk about PyScript development in the open. Most of the maintainers regularly participate in the call, and everybody is welcome to join.
+
+Every other Thursday at 16:00 UTC there is the _PyScript FUN_ call: this is a call in which everybody is encouraged to show what they did with PyScript.
+
+For more details on how to join the calls and up to date schedule, consult the official calendar:
+
+-   [Google calendar](https://calendar.google.com/calendar/u/0/embed?src=d3afdd81f9c132a8c8f3290f5cc5966adebdf61017fca784eef0f6be9fd519e0@group.calendar.google.com&ctz=UTC) in UTC time;
+-   [iCal format](https://calendar.google.com/calendar/ical/d3afdd81f9c132a8c8f3290f5cc5966adebdf61017fca784eef0f6be9fd519e0%40group.calendar.google.com/public/basic.ics).
+
 ## Resources

 -   [Official docs](https://docs.pyscript.net)
--- a/pyscript.core/src/hooks.js
+++ b/pyscript.core/src/hooks.js
@@ -45,6 +45,19 @@ export const createFunction = (self, name) => {
 const SetFunction = typedSet({ typeof: "function" });
 const SetString = typedSet({ typeof: "string" });

+const inputFailure = `
+    import builtins
+    def input(prompt=""):
+        raise Exception("\\n           ".join([
+            "input() doesn't work when PyScript runs in the main thread.",
+            "Consider using the worker attribute: https://docs.pyscript.net/2023.11.1/user-guide/workers/"
+        ]))
+
+    builtins.input = input
+    del builtins
+    del input
+`;
+
 export const hooks = {
    main: {
        /** @type {Set<function>} */
@@ -60,7 +73,7 @@ export const hooks = {
        /** @type {Set<function>} */
        onAfterRunAsync: new SetFunction(),
        /** @type {Set<string>} */
-        codeBeforeRun: new SetString(),
+        codeBeforeRun: new SetString([inputFailure]),
        /** @type {Set<string>} */
        codeBeforeRunAsync: new SetString(),
        /** @type {Set<string>} */
--- a/pyscript.core/test/input.html
+++ b/pyscript.core/test/input.html
@@ -0,0 +1,21 @@
+<!doctype html>
+<html lang="en">
+    <head>
+        <meta charset="UTF-8" />
+        <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+        <title>PyScript Next</title>
+        <script>
+            addEventListener("py:ready", console.log);
+        </script>
+        <link rel="stylesheet" href="../dist/core.css">
+        <script type="module" src="../dist/core.js"></script>
+    </head>
+    <body>
+        <py-script>
+            input("what's your name?")
+        </py-script>
+        <mpy-script>
+            input("what's your name?")
+        </mpy-script>
+    </body>
+</html>
--- a/pyscript.core/tests/integration/test_01_basic.py
+++ b/pyscript.core/tests/integration/test_01_basic.py
@@ -93,6 +93,19 @@ class TestBasic(PyScriptTest):
        )
        assert self.console.log.lines[-1] == "hello pyscript"

+    @only_main
+    def test_input_exception(self):
+        self.pyscript_run(
+            """
+            <script type="py">
+                input("what's your name?")
+            </script>
+            """
+        )
+        self.check_py_errors(
+            "Exception: input() doesn't work when PyScript runs in the main thread."
+        )
+
    @skip_worker("NEXT: exceptions should be displayed in the DOM")
    def test_python_exception(self):
        self.pyscript_run(
Author	SHA1	Message	Date
Peter W	39725c1384	Use latest instead	2023-11-21 11:11:57 -06:00
Peter W	48c5158b46	Fix 404 in main README.md	2023-11-21 11:09:48 -06:00
Antonio Cuni	4b89c84692	use UTC time (#1859 )	2023-11-15 16:00:09 +01:00
Antonio Cuni	df68449b82	Improve README and and mention the community calls (#1858 ) Improve the readme in two ways: - remove the mention to <py-repl>, and shows a quick summary of the various ways of running Python code - add a link to the google calendar which contains the community calls	2023-11-15 12:10:52 +01:00
Andrea Giammarchi	48e3383f66	Fix #1841 - Provide a better error when input is used (#1857 )	2023-11-14 15:25:17 +01:00