This is amazing!!!!!!

Great job, keep at it

Awesome ❤️

This new release is a very big milestone for PyScript, because it unlocks a lot of potential.
I know that everybody in the team has their own favorite feature of PyScript Next: some like the MicroPython support, some the smaller download size, some the faster startup.

Let me share with the community what I think it is the most exciting feature: PyScript next allows to transparently run Python code inside a webworker, and thanks to the magic wonders of xworker.sync, it allows to fill the gap between the async-first nature of the browser and the sync-first nature of the vast majority of Python code around.

In PyScript classic, it was technically impossible to support or even emulate a lot of basic blocking APIs which Python programmers take for granted, such as:

• input() for reading a string from the keyboard
• any kind of synchronous socket such as requests.get() or sock.recv()
• any kind of support for debuggers (including, but not limited to, pdb.set_trace())

With Next, all of the above is possible, when you run in a worker. The following are a couple of demos which demonstrate the potential:

• https://antocuni.pyscriptapps.com/pyterminal-poc/v1/: this revives py-terminal by using xterm.js and a blocking version of input() based on xworker.sync: the result is that you can for example run pdb (or even pdb++, like in this example)
• https://antocuni.pyscriptapps.com/pytest-in-pyterminal/v1/: similar to the above, but shows how to run an entire pytest session inside a terminal
• https://antocuni.pyscriptapps.com/gui-debugger/v1/: this is a very raw proof of concept, but shows how to connect a GUI debugger running in the main thread with a user program running in a worker. The GUI is very basic and ugly, but you can imagine having one with all the bells&whistles that normal debuggers have.

The plan is to re-integrate the py-terminal into pyscript in the next weeks.