Pyskool
In 1984, Microsphere published Skool Daze, a game for the Sinclair ZX Spectrum. In 1985, the sequel Back to Skool was published.
Each game is based in a boys’ school (though Back to Skool adds a playground and a girls’ school) and revolves around the antics of Eric, the hero. In Skool Daze, Eric must steal his report card from the school safe - the combination of which must be extracted from the teachers’ brains using flashing shields or, in the case of the history teacher, post-hypnotic suggestion. In Back to Skool, Eric must get his report card back into the school safe, this time with the extra help provided by a water pistol, stinkbombs, a bike, mice, a frog and a girlfriend.
Pyskool is a re-implementation of these classic games in Pygame, with the aim of making them easy to customise by editing configuration files or - for more advanced customisation - writing some Python code.
Requirements
Pyskool requires Python 3.10+ and Pygame (version 2.0.2+).
On Linux/*BSD, Pygame is available via the package management system: the python3-pygame package on most Linux distros, the devel/py-game port on FreeBSD and NetBSD, and the devel/pygame port on OpenBSD.
Windows and Mac OS X users should take care to select the Pygame installer that matches the version of Python that is installed.
Running Pyskool
Pyskool is actually five separate games:
Skool Daze (skool_daze.py)
Back to Skool (back_to_skool.py)
Skool Daze Take Too (skool_daze_take_too.py)
Ezad Looks (ezad_looks.py)
Back to Skool Daze (back_to_skool_daze.py)
Before playing any of these games for the first time, the required images, ini files and sound files will need to be created. This can be done by using the --setup option; for example:
$ skool_daze.py --setup
This will:
download TZX files from the sources listed in images.ini and use them to create the required images in ~/.pyskool/images
write the required ini files in ~/.pyskool/ini
write the required sound files in ~/.pyskool/sounds
After that, Pyskool can be run in Skool Daze mode:
$ skool_daze.py
Playing Pyskool
The keys to move Eric around are:
‘q’ or up arrow - go up stairs, or continue walking in the same direction
‘a’ or down arrow - go down stairs, or continue walking in the same direction
‘o’ or left arrow - left
‘p’ or right arrow - right
‘f’ - fire catapult
‘h’ - hit
‘j’ - jump
‘s’ - sit/stand
‘w’ - write on a blackboard (press Enter/Return to finish)
Other useful keys are:
Escape - quit the game
End - pause/resume
Insert - take a screenshot
F2 - save the game
F6 - load the most recently saved game
F11 - switch between full-screen and windowed mode
F12 - show/hide the menu
For full instructions, see the documentation.
1 maintainer
Metadata
1 maintainer
Release files for pyskool 1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pyskool-1.3.tar.gz | 251.2 kB | Without provenance | Details for pyskool-1.3.tar.gz |
Release files / pyskool-1.3.tar.gz
| Download URL | pyskool-1.3.tar.gz |
|---|---|
| Size | 251.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6247544ffe10ba3eb82a7c7a58d8d3574dd382adf27f23013fb9be0a4220c5f6
|
|
BLAKE2b-256 checksum How to use checksums |
76d3d7335b74afbb88befd2da7c6e992e93894f12a3cfc7b48a5c9d0b5dcca9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.5
|
Security for pyskool 1.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
