Platforms
Where each package runs
Where |
Package |
How it’s tested |
|---|---|---|
CPython 3.11–3.14 on Linux x86_64 (manylinux_2_28) |
compiled wheel, |
the full tests run on every change, against both packages |
CPython 3.11–3.14 on Linux aarch64 (manylinux_2_28), such as 64-bit Raspberry Pi OS |
compiled wheel |
each release checks the wheel loads its compiled module |
CPython 3.11–3.14 on Windows x86_64 |
compiled wheel |
each release checks the wheel loads its compiled module |
CPython 3.13–3.14 on Android, arm64-v8a and x86_64 |
compiled wheel |
the wheel builds; it isn’t run on a device |
Pyodide, CPython 3.13 and 3.14 |
compiled wheel ( |
the wheel builds; micropip picks the one for your Pyodide |
MicroPython, any port |
pure-Python, from mip |
the compiled module’s tests and the comparison against |
CircuitPython |
pure-Python, copied to |
not tested automatically |
macOS, and 32-bit Linux on ARM |
pure-Python |
no compiled wheel: copy |
On a Raspberry Pi, the aarch64 wheel has run on a Pi 4 and a Pi 3 B+. A Pi 5 runs the same 64-bit Raspberry Pi OS and should take the same wheel, but nobody has tried it yet. If you do, open an issue and say what worked.
The compiled module can also be built into MicroPython or CircuitPython
firmware; CONTRIBUTING.md
has the steps. pygraphics.implementation() tells you which one you have:
native_cmod for the compiled module, pygraphics_python for the pure one.
Names only the pure-Python package has
Everything in pygraphics.__all__ is in both packages, except four names
that write or read Python source. The compiled package leaves them out:
Name |
What it does |
|---|---|
|
writes a framebuffer as an importable |
|
the same, as a method |
|
makes a framebuffer from such a module’s |
|
the same, from the imported module |
Old names
If you installed pygraphics under an earlier name, uninstall that and install the current one.
Now |
Earlier |
|
|---|---|---|
Import |
|
|
pip (compiled) |
|
|
mip |
|
|