PocketPy as a lightweight alternative to Pyodide for Pyxel

[CodeLazier]

Currently Pyxel’s web export relies on Pyodide, which makes the package quite large (~9MB+) and slow to start. This can be a barrier for small retro games.

I’d like to suggest exploring PocketPy
as an alternative scripting backend:

Much smaller size (1–2MB WASM vs ~9MB with Pyodide).

Faster startup and execution (closer to Lua-level performance).

Good fit for Pyxel’s design goals: lightweight, portable, retro-friendly.

The main trade-off is reduced compatibility (no full Python stdlib), but for game logic this might be enough.

[kitao]

Thank you for your information.
It really looks interesting. I don't know the best way to use it with Rust yet, I'll check it.

[merwok]

I think it’s more limited and much less mature.

It seems to position itself as a restricted implementation of Python (like MicroPython), not a build of CPython. It does not cover the full language (no finally!) or stdlib.

(Also its stability is questionable: its functions use the Py prefix that is reserved by Cpython for itself!)

[CodeLazier]

pocketpy v2.0.1 the try/except/finally syntax is supported, so that’s no longer an issue.

as for the Py* prefix, that’s not really a stability problem PocketPy is a standalone interpreter, so there’s no conflict with CPython’s C API. It’s just a naming convention.

PocketPy and CPython are completely unrelated they are two different products. They’re only placed side by side for performance comparison.

[CodeLazier]

I think it’s more limited and much less mature.

PocketPy is a mature and stable project. One of the most notable fantasy consoles uses PocketPy, and the hundreds of games built on it have fully proven its reliability. With TIC-80 supporting Python as a scripting language while still remaining lightweight and fast, this serves as a strong validation of PocketPy’s robustness and efficiency.

tic-80 python.c

[merwok]

Thanks for correcting my impressions!