Installation overview¶
pydisplay supports three install channels. Pick based on whether you need the full repo, source files on device, or precompiled bytecode.
Comparison¶
| Channel | Format | Install tool | Includes examples | Includes add_ons |
|---|---|---|---|---|
| Full clone | Entire repo | git clone |
Yes | Yes |
| GitHub MIP | Source .py |
mip / mpremote mip |
Optional (examples.json) |
Yes (add_ons.json) |
| micropython-lib MIP | Precompiled .mpy |
mip with custom index |
No | No |
The installer.py script combines GitHub and micropython-lib installs in one call — recommended for MicroPython boards.
What gets installed¶
Core libraries (under src/lib/):
displaysys— display drivers (BusDisplay, SDL2Display, etc.)eventsys— input events and device brokersgraphics— extended drawing helperspalettes— color palettesmultimer— cross-platform timers (CPython, MicroPython, CircuitPython unix). Asyncio timers:multimer.aio— see multimer
Optional packages:
add_ons— framebuf shim, console, pdwidgets, displaybuf, etc.examples— demo scriptsspibus/i80bus— MicroPython bus drivers (viper; GitHub only)
Board support:
board_config.pyper hardware — see board configs- Display and touch drivers from
drivers/
PyPI / pip¶
CPython wheels are built to TestPyPI for maintainer testing. End-user pip install is not documented yet. Use a full clone or desktop quick start.
After installing¶
- Provide or install a
board_config.pymatching your hardware. - Follow the quick start for your platform:
- ESP32 / MCU
- Desktop CPython
- Wokwi
Troubleshooting¶
See Troubleshooting for import errors, MIP failures, and display issues.