You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
print("Hello terminal") # this goes to the terminal
37
+
</script>
38
+
</body>
32
39
```
33
40
34
-
You can then use PyScript components in your html page. PyScript currently implements the following elements:
41
+
You can then use PyScript components in your html page. PyScript currently offers various ways of running Python code:
35
42
36
-
-`<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
37
-
-`<py-repl>`: creates a REPL component that is rendered to the page as a code editor and allows users to write executable code
43
+
-`<script type="py">`: can be used to define python code that is executable within the web page.
44
+
-`<script type="py" src="hello.py">`: same as above, but the python source is fetched from the given URL.
45
+
-`<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.
46
+
-`<script type="py" terminal worker>`: run Python inside a web worker: the terminal if fully functional and `input()` works.
47
+
-`<py-script>`: same as `<script type="py">`, but it is not recommended because if the code contains HTML tags, they could be parsed wrongly.
48
+
-`<script type="mpy">`: same as above but use MicroPython instead of Python.
38
49
39
-
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.
50
+
Check out the [official docs](https://docs.pyscript.net)for more detailed documentation.
40
51
41
52
## How to Contribute
42
53
43
54
Read the [contributing guide](CONTRIBUTING.md) to learn about our development process, reporting bugs and improvements, creating issues and asking questions.
44
55
45
56
Check out the [developing process](https://docs.pyscript.net/latest/contributing) documentation for more information on how to setup your development environment.
46
57
58
+
## Community calls and events
59
+
60
+
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.
61
+
62
+
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.
63
+
64
+
For more details on how to join the calls and up to date schedule, consult the official [Google calendar](https://calendar.google.com/calendar/u/0/embed?src=d3afdd81f9c132a8c8f3290f5cc5966adebdf61017fca784eef0f6be9fd519e0@group.calendar.google.com&ctz=Europe/Berlin) page (also available in [iCal format](https://calendar.google.com/calendar/ical/d3afdd81f9c132a8c8f3290f5cc5966adebdf61017fca784eef0f6be9fd519e0%40group.calendar.google.com/public/basic.ics)).
0 commit comments