This week I’ve kept working on reflected and started testing latest MicroPython capabilities after PyScript release.
I’ve also helped moving forward the MR related to weakref module around that release
I’ve also discussed internally results from various polls and asked in social medias if anyone had issues with Android WebViews.
Russel also confirmed everything looks great, after I’ve gaven to him the basic setup that is running also on pythonanywhere.
I have prepared a few demoes around latest MicroPython features and presented these during our call.
We had an internal presentation explaining the current status of our Q1 goal, my quick summary is that there is progress but still a lot of work to do: we are on track but there’s not much time left …
Because I forgot to present PEP750 that landed in MicroPython, I am currently trying to present something later on this afternoon but in the meantime, Nicholas asked me if a @pyscript/bridge like functionality could be exposed for a Python backend (no WASM runtime, real Python via FastAPI, Django, Flask and what not).
TL;DR the bridge uses heavily Pyodide capabilities and features but as “Plan B” we could, and likely should, be able to fallback to something extremely simple that doesn’t involve WASM runtimes at all, it just uses JS natively on the browser side, exposing with extreme easy any possible API or method from the backend so I’ve worked on something that I believe could deliver that feature/fallback with relative ease and I will present it during today PyScript Fun community call: jstamp.
Tomorrow I’ll work 2/3rd of the day but I’ll make up some time over the weekend to keep moving forward with the reflected project and the pure MicroPython friendly implemnetation (for the Worker side, the other side will be 100% C-Python focused).
And that’s a wrap for this week: a lot of meetings, demoes, presentations … I hope the next one will be more focused on code and less abstracts 👋