Add pypy wheel building and publishing to Github actions workflow and Makefile #618
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The biggest weakness of pyxel compared to other platforms like PICO-8 is the intrinsic slowness of python compared to languages like Lua which can leverage LuaJit.
The PyPy project leverages JIT, but not all python packages publish pypy wheels. Pyxel is one such project. This is my first pass attempt to alter the CI/CD pipeline to publish pypy wheels for the community to give users the option to leverage the speed of pypy.
Pyxel is a perfect candidate for leveraging pypy since most pyxel games will be completely self-contained and not necessarily need to bring in dependencies from the Cpython ecosystem.
When using package managers like
uv
switching the python backend to pypy should be as easy as putting[email protected]
in the.python-version
file.I was able to run this CI pipeline myself to generate python wheels for pypy here. I successfully tested the
pyxel-2.3.10-pp310-pypy310_pp73-win_amd64.whl
wheel on a windows PC viauv pip install
and it seems to work fine.