Files
libretro/emulators/pyxel.yml
T
Abdessamad Derraz 4231902a6c docs: write prose without dashes or semicolons
Profiles, the wiki, comments, docstrings, command output and schema descriptions carried em-dashes, clause-joining semicolons, unicode arrows, box-drawing banners and check-mark glyphs. Each sentence was rewritten rather than having its character swapped. Hashes, paths, source_ref values and every cited file:line are unchanged, which a comparison of each parsed profile against the previous revision confirms.

validate_pr comments now say PASS and FAIL in words, and source_ref values in a profile's structured blocks render as code. test_prose_style fails if any of these comes back, in tracked files or in the generated site.
2026-10-19 06:47:31 +02:00

38 lines
1.5 KiB
YAML

emulator: Pyxel
type: standalone
core_classification: game_engine
source: "https://github.com/kitao/pyxel"
upstream: "https://github.com/kitao/pyxel"
profiled_date: "2026-10-04"
source_commit: "50f9bd77780c993aca62b5b221766bde5791081d"
upstream_gone: "github.com/kitao/pyxel answers HTTP 404 to the API and the web, with no redirect. Observed 2026-10-18, no mirror found."
core_version: "v2.9.9"
display_name: "Pyxel"
cores: [pyxel]
systems: []
verification: existence
notes: |
Retro game engine for Python by Takashi Kitao. The engine is a Python
package with a Rust-based extension (crates/pyxel-core, built via maturin).
Pyxel programs are either .py scripts that import pyxel or self-contained
.pyxapp bundles (zip archives containing a startup script plus assets).
There is no external BIOS, firmware, or retail data to collect. Everything
the engine needs ships inside the Python wheel:
python/pyxel/: Python API, fonts, shader, examples
crates/pyxel-core/: Rust engine (compiled as pyxel_extension)
crates/pyxel-platform/: SDL2 wrapper
crates/pyxel-wrapper/: Python to Rust glue (PyO3)
Batocera's packaging (package/batocera/emulators/python-pyxel/python-pyxel.mk)
installs the wheel into site-packages, drops the examples, and provides a
pyxel.keys evmapy layout. The content run by Pyxel is the user's .pyxapp or
.py file, which plays the role of a cartridge. Those are user content, not
pack contents.
The engine refuses nothing on startup: a bare `pyxel init` plus a user
script is enough to run.
files: []