Improve README and and mention the community calls #1858
Conversation
for more information, see https://pre-commit.ci
|
I see that the google calendar URL contains a reference to the "Berlin timezone": Could someone located in a different timezone check what happen when they open the page? Are the times shown in their local timezone or Berlin's? |
|
I am OK with this update but is there any reason we don't mention at all MicroPython? 🤔 |
We do :) |
I see, I was just thinking maybe we could mention that at the beginning as we only mention Pyodide ... nothing urgent or blocking though |
ah yes, that's a good point. But yes, I think it'd be a good idea to mention MicroPython at the top |
I'm probably late but yeah this is showing Berlin time zone, I think we could change it to UTC to show UTC and when you click "more details" it will take you to google calendar and show your timezone 🤔 There might be a settings on the calendar itself to yse Viewer's timezone 🤔 |
| - `<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. |
There was a problem hiding this comment.
Would you guys mind adding a reason (or pointer to one) about why a user would choose to run python in the worker instead of as main ?
|
I think you are right, on Pyscript events the Decemebr 5th meeting shows as "5:30pm Py script Community Call" but when I added to my calendar it shows as 8:30- 9:30am.
|
Improve the readme in two ways:
<py-repl>, and shows a quick summary of the various ways of running Python code