Extending MicroPython: Using C for good!
summary
Claims that MicroPython performance improves by selectively dropping into C are shown end to end: a Project Nayuki QR implementation is ported, Python prototype runs ~1500 ms for small codes while the C-wrapped version runs ~11 ms; wrapper work includes building MicroPython C structs and marshalling code and exposing a class-like API; deployment options cover frozen .mpy, upip libraries, and native modules for runtime-loading; demoed on an ESP32 TinyPICO serving QR pages using Project Nayuki C core.
AI-written summary · about
chapters (6)
- 0:00Start
- 5:49Dessert: Native modules
- 11:27MicroPython Ports
- 17:06Optimisations: @native, @viper, Assembly
- 20:35Porting Python libraries to MicroPython
- 30:45Marshalling 101
related talks
27mYou can't do that in MicroPython!
32mUsing MicroPython in the wild
30m"MicroPython: The best bits!"
51mMicroPython: a journey from Kickstarter to Space
54mExtending MicroPython with Rust: Two Worlds Collide
22mPyPy and the future of the Python ecosystem
34mUsing Python to enter the world of Microcontrollers
27mMicroPython: Embedded programming for everyone