pgzero-plus 0.0.1a1__tar.gz

pgzero_plus-0.0.1a1/COPYING

@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

pgzero_plus-0.0.1a1/PKG-INFO

@@ -0,0 +1,259 @@
+Metadata-Version: 2.4
+Name: pgzero-plus
+Version: 0.0.1a1
+Summary: An enhanced fork of Pygame Zero with additional features for teaching and developing 2D games
+Author-email: Michael D'Argenio <mjdargen@gmail.com>
+License-Expression: LGPL-3.0-or-later
+Project-URL: Homepage, https://github.com/mjdargen/pgzero
+Project-URL: Documentation, https://pygame-zero.readthedocs.io/
+Project-URL: Source, https://github.com/mjdargen/pgzero
+Project-URL: Issues, https://github.com/mjdargen/pgzero/issues
+Keywords: pygame,pgzero,games,education
+Classifier: Intended Audience :: Education
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Education
+Classifier: Topic :: Games/Entertainment
+Requires-Python: <3.14,>=3.6
+Description-Content-Type: text/markdown
+License-File: COPYING
+Requires-Dist: pygame>=2.6.1
+Requires-Dist: numpy
+Requires-Dist: pyfxr>=0.3.0
+Requires-Dist: importlib-metadata==4.8.3; python_version < "3.8"
+Dynamic: license-file
+
+# Pygame Zero Plus
+
+**Pygame Zero Plus** (`pgzero-plus`) is an independent fork of [Pygame Zero](https://github.com/lordmauve/pgzero), a beginner-friendly Python game development framework that reduces boilerplate code.
+
+This fork adds features and quality-of-life improvements for introductory computer science and game design courses while retaining the familiar Pygame Zero API, including `Actor`, `screen`, and `pgzrun`.
+
+## What's New
+
+- **Enhanced Actors:** Scaling, flipping, opacity, and customizable collision rectangles.
+- **Sprite Animations:** `Sprite` and `SpriteActor` classes for animated sprite sheets.
+- **Tilemaps:** Loading and rendering maps created with [Tiled Map Editor](https://www.mapeditor.org/), including tilesets and tile transformations.
+- **Game Management:** A `Game` object for tracking scores, levels, game states, and restarting games.
+
+## Installation
+
+The PyPI distribution is named `pgzero-plus`, but it provides the same `pgzero` Python package and `pgzrun` command as the original Pygame Zero. **Do not install both distributions in the same Python environment.**
+
+### Install or Update
+
+Once published on PyPI:
+
+**Windows:**
+
+```bash
+python -m pip install --upgrade pgzero-plus
+```
+
+**macOS / Linux:**
+
+```bash
+python3 -m pip install --upgrade pgzero-plus
+```
+
+### Switching from Pygame Zero or an Older Fork
+
+If you previously installed `pgzero` or `pgzero-mjd`, uninstall any overlapping distributions before installing Pygame Zero Plus. This also helps repair environments where multiple forks have been installed together.
+
+**Windows:**
+
+```bash
+python -m pip uninstall -y pgzero pgzero-mjd pgzero-plus
+python -m pip install pgzero-plus
+```
+
+**macOS / Linux:**
+
+```bash
+python3 -m pip uninstall -y pgzero pgzero-mjd pgzero-plus
+python3 -m pip install pgzero-plus
+```
+
+`--force-reinstall` does **not** remove a differently named distribution, so it is not a substitute for uninstalling the original `pgzero` package.
+
+### Running Games
+
+Pygame Zero Plus supports running games as regular Python scripts, including with the Run button in VS Code.
+
+Start your program with:
+
+```python
+import pgzrun
+from pgzero.builtins import *
+```
+
+The explicit `pgzero.builtins` import helps editors such as VS Code (Pylance) recognize names like `Actor` and `screen`.
+
+Define your variables and functions, such as `start()`, `draw()`, and `update()`, then end the program with:
+
+```python
+pgzrun.go()
+```
+
+Run the script through your editor or with:
+
+```bash
+python game.py
+```
+
+Alternatively, use the traditional Pygame Zero command:
+
+```bash
+pgzrun game.py
+```
+
+## Development
+
+Clone the repository:
+
+```bash
+git clone https://github.com/mjdargen/pgzero.git
+cd pgzero
+```
+
+Install the fork in editable mode **and** install all development tools with one command:
+
+```bash
+python -m pip install -r requirements-dev.txt
+```
+
+`requirements-dev.txt` includes `-e .`, which installs the local package and its runtime dependencies. Source changes are available immediately without rebuilding the wheel. If the original `pgzero` is installed in this environment, uninstall it first as described above.
+
+### Pre-commit Checks
+
+[Pre-commit](https://pre-commit.com/) checks whitespace, file endings, YAML/TOML syntax, merge conflict markers, and accidentally added large files.
+
+Activate it **once per clone**, after installing the development dependencies:
+
+```bash
+python -m pre_commit install
+```
+
+It then runs automatically on staged files before each `git commit`. If a hook modifies a file, review it with `git diff`, stage the fix with `git add`, and retry the commit.
+
+To check all tracked files manually at any time:
+
+```bash
+python -m pre_commit run --all-files
+```
+
+Using `python -m pre_commit` avoids Windows PATH issues where the `pre-commit` command is not recognized.
+
+### Testing
+
+Run all tests from the repository root:
+
+```bash
+python -m pytest
+```
+
+For detailed output or one test file:
+
+```bash
+python -m pytest -v
+python -m pytest test/test_actor.py
+```
+
+### Documentation
+
+Documentation is written in [Sphinx](https://www.sphinx-doc.org/) using the `.rst` files in `doc/`. Update these pages when features or behavior change, and add new pages to `doc/index.rst` so they appear in the navigation.
+
+Build and preview locally from the repository root:
+
+```bash
+python -m sphinx -b html doc doc/_build/html
+```
+
+On Windows (PowerShell), open the generated documentation with:
+
+```powershell
+start doc/_build/html/index.html
+```
+
+On macOS or Linux, open that HTML file in your browser. The Sphinx configuration lives in `doc/conf.py`.
+
+Once this repository is connected to [Read the Docs](https://readthedocs.org/), its `.readthedocs.yaml` configuration allows the hosted documentation to rebuild automatically after changes are pushed. GitHub Actions verifies that the documentation builds; Read the Docs hosts and publishes the website.
+
+### Automated Checks on GitHub
+
+The [Code Checks workflow](https://github.com/mjdargen/pgzero/actions) (`.github/workflows/checks.yml`) runs automatically on pushes to `main` and on pull requests. It runs pre-commit, pytest, Sphinx, the package build, and distribution validation.
+
+These checks run **after** a push, so a failing check does not undo the push. Check the Actions page for results and fix any failures before publishing a release.
+
+## Building and Verification
+
+The automated release workflow builds distributions for publishing, so **manual builds are optional** during everyday development. To check a release locally, run:
+
+```bash
+python -m pre_commit run --all-files
+python -m pytest
+python -m sphinx -b html doc doc/_build/html
+python -m build
+python -m twine check --strict dist/*
+```
+
+The wheel (`.whl`) and source archive (`.tar.gz`) are written to `dist/`. Clear out older distributions from `dist/` before building a new version so you do not accidentally inspect or upload old files.
+
+### Verify the Built Wheel
+
+Install the built wheel in a **fresh virtual environment** to check the distribution itself instead of your editable development installation. The example filename below is for version `0.1.0`; update it when the version changes.
+
+**Windows (PowerShell):**
+
+```powershell
+python -m venv .venv-wheel-check
+.\.venv-wheel-check\Scripts\python.exe -m pip install dist/pgzero_plus-0.1.0-py3-none-any.whl
+.\.venv-wheel-check\Scripts\python.exe -m pip check
+.\.venv-wheel-check\Scripts\python.exe -c "import pgzero, pgzrun; print(pgzero.__file__)"
+```
+
+**macOS / Linux:**
+
+```bash
+python3 -m venv .venv-wheel-check
+.venv-wheel-check/bin/python -m pip install dist/pgzero_plus-0.1.0-py3-none-any.whl
+.venv-wheel-check/bin/python -m pip check
+.venv-wheel-check/bin/python -c "import pgzero, pgzrun; print(pgzero.__file__)"
+```
+
+**Python 3.6 compatibility:** This fork targets Python 3.6 through 3.13, including older Codio environments. The modern build backend does not support building from source on Python 3.6. Before a release, install the **built wheel** in Codio and run a representative game there; passing tests on Python 3.13 does not establish compatibility with Python 3.6.
+
+## Publishing Releases
+
+GitHub Actions handles publishing through `.github/workflows/release.yml`. A new package is **not** published on every push to `main`; publishing starts only when you push a version tag.
+
+### One-time PyPI Setup
+
+1. Create a GitHub repository environment named `pypi` under **Settings → Environments**.
+2. Configure [PyPI Trusted Publishing](https://docs.pypi.org/trusted-publishers/) for project `pgzero-plus`, GitHub owner `mjdargen`, repository `pgzero`, workflow `release.yml`, and environment `pypi`. For a first release, use a _pending trusted publisher_ if the project has not yet been created on PyPI.
+
+This allows GitHub Actions to publish without storing a PyPI API token.
+
+### Create a Release
+
+1. Set the new `version` in `pyproject.toml`. For example, `version = "0.1.0"`.
+2. Commit and push your changes to `main`, then confirm that **Code Checks** passes on the [Actions page](https://github.com/mjdargen/pgzero/actions).
+3. Create and push a Git tag **matching** that version, with a leading `v`:
+
+```bash
+git switch main
+git pull
+git tag -a v0.1.0 -m "Release v0.1.0"
+git push origin v0.1.0
+```
+
+The release workflow verifies the version, runs the checks, builds the wheel and source archive, publishes to PyPI, and creates a GitHub Release with the built files attached. If a check or build fails, publishing stops.
+
+For a later release, update the version number and use its matching tag (for example, `0.1.1` and `v0.1.1`). Use patch releases for bug fixes and minor releases for new features. **PyPI does not allow replacing files for an existing published version.**
+
+## Credits & License
+
+This project is an independent fork of [Pygame Zero](https://github.com/lordmauve/pgzero), originally developed by Daniel Pope and contributors.
+
+Original documentation: https://pygame-zero.readthedocs.io/
+
+Licensed under the GNU Lesser General Public License v3.0 or later (LGPL-3.0-or-later).

pgzero_plus-0.0.1a1/README.md

@@ -0,0 +1,235 @@
+# Pygame Zero Plus
+
+**Pygame Zero Plus** (`pgzero-plus`) is an independent fork of [Pygame Zero](https://github.com/lordmauve/pgzero), a beginner-friendly Python game development framework that reduces boilerplate code.
+
+This fork adds features and quality-of-life improvements for introductory computer science and game design courses while retaining the familiar Pygame Zero API, including `Actor`, `screen`, and `pgzrun`.
+
+## What's New
+
+- **Enhanced Actors:** Scaling, flipping, opacity, and customizable collision rectangles.
+- **Sprite Animations:** `Sprite` and `SpriteActor` classes for animated sprite sheets.
+- **Tilemaps:** Loading and rendering maps created with [Tiled Map Editor](https://www.mapeditor.org/), including tilesets and tile transformations.
+- **Game Management:** A `Game` object for tracking scores, levels, game states, and restarting games.
+
+## Installation
+
+The PyPI distribution is named `pgzero-plus`, but it provides the same `pgzero` Python package and `pgzrun` command as the original Pygame Zero. **Do not install both distributions in the same Python environment.**
+
+### Install or Update
+
+Once published on PyPI:
+
+**Windows:**
+
+```bash
+python -m pip install --upgrade pgzero-plus
+```
+
+**macOS / Linux:**
+
+```bash
+python3 -m pip install --upgrade pgzero-plus
+```
+
+### Switching from Pygame Zero or an Older Fork
+
+If you previously installed `pgzero` or `pgzero-mjd`, uninstall any overlapping distributions before installing Pygame Zero Plus. This also helps repair environments where multiple forks have been installed together.
+
+**Windows:**
+
+```bash
+python -m pip uninstall -y pgzero pgzero-mjd pgzero-plus
+python -m pip install pgzero-plus
+```
+
+**macOS / Linux:**
+
+```bash
+python3 -m pip uninstall -y pgzero pgzero-mjd pgzero-plus
+python3 -m pip install pgzero-plus
+```
+
+`--force-reinstall` does **not** remove a differently named distribution, so it is not a substitute for uninstalling the original `pgzero` package.
+
+### Running Games
+
+Pygame Zero Plus supports running games as regular Python scripts, including with the Run button in VS Code.
+
+Start your program with:
+
+```python
+import pgzrun
+from pgzero.builtins import *
+```
+
+The explicit `pgzero.builtins` import helps editors such as VS Code (Pylance) recognize names like `Actor` and `screen`.
+
+Define your variables and functions, such as `start()`, `draw()`, and `update()`, then end the program with:
+
+```python
+pgzrun.go()
+```
+
+Run the script through your editor or with:
+
+```bash
+python game.py
+```
+
+Alternatively, use the traditional Pygame Zero command:
+
+```bash
+pgzrun game.py
+```
+
+## Development
+
+Clone the repository:
+
+```bash
+git clone https://github.com/mjdargen/pgzero.git
+cd pgzero
+```
+
+Install the fork in editable mode **and** install all development tools with one command:
+
+```bash
+python -m pip install -r requirements-dev.txt
+```
+
+`requirements-dev.txt` includes `-e .`, which installs the local package and its runtime dependencies. Source changes are available immediately without rebuilding the wheel. If the original `pgzero` is installed in this environment, uninstall it first as described above.
+
+### Pre-commit Checks
+
+[Pre-commit](https://pre-commit.com/) checks whitespace, file endings, YAML/TOML syntax, merge conflict markers, and accidentally added large files.
+
+Activate it **once per clone**, after installing the development dependencies:
+
+```bash
+python -m pre_commit install
+```
+
+It then runs automatically on staged files before each `git commit`. If a hook modifies a file, review it with `git diff`, stage the fix with `git add`, and retry the commit.
+
+To check all tracked files manually at any time:
+
+```bash
+python -m pre_commit run --all-files
+```
+
+Using `python -m pre_commit` avoids Windows PATH issues where the `pre-commit` command is not recognized.
+
+### Testing
+
+Run all tests from the repository root:
+
+```bash
+python -m pytest
+```
+
+For detailed output or one test file:
+
+```bash
+python -m pytest -v
+python -m pytest test/test_actor.py
+```
+
+### Documentation
+
+Documentation is written in [Sphinx](https://www.sphinx-doc.org/) using the `.rst` files in `doc/`. Update these pages when features or behavior change, and add new pages to `doc/index.rst` so they appear in the navigation.
+
+Build and preview locally from the repository root:
+
+```bash
+python -m sphinx -b html doc doc/_build/html
+```
+
+On Windows (PowerShell), open the generated documentation with:
+
+```powershell
+start doc/_build/html/index.html
+```
+
+On macOS or Linux, open that HTML file in your browser. The Sphinx configuration lives in `doc/conf.py`.
+
+Once this repository is connected to [Read the Docs](https://readthedocs.org/), its `.readthedocs.yaml` configuration allows the hosted documentation to rebuild automatically after changes are pushed. GitHub Actions verifies that the documentation builds; Read the Docs hosts and publishes the website.
+
+### Automated Checks on GitHub
+
+The [Code Checks workflow](https://github.com/mjdargen/pgzero/actions) (`.github/workflows/checks.yml`) runs automatically on pushes to `main` and on pull requests. It runs pre-commit, pytest, Sphinx, the package build, and distribution validation.
+
+These checks run **after** a push, so a failing check does not undo the push. Check the Actions page for results and fix any failures before publishing a release.
+
+## Building and Verification
+
+The automated release workflow builds distributions for publishing, so **manual builds are optional** during everyday development. To check a release locally, run:
+
+```bash
+python -m pre_commit run --all-files
+python -m pytest
+python -m sphinx -b html doc doc/_build/html
+python -m build
+python -m twine check --strict dist/*
+```
+
+The wheel (`.whl`) and source archive (`.tar.gz`) are written to `dist/`. Clear out older distributions from `dist/` before building a new version so you do not accidentally inspect or upload old files.
+
+### Verify the Built Wheel
+
+Install the built wheel in a **fresh virtual environment** to check the distribution itself instead of your editable development installation. The example filename below is for version `0.1.0`; update it when the version changes.
+
+**Windows (PowerShell):**
+
+```powershell
+python -m venv .venv-wheel-check
+.\.venv-wheel-check\Scripts\python.exe -m pip install dist/pgzero_plus-0.1.0-py3-none-any.whl
+.\.venv-wheel-check\Scripts\python.exe -m pip check
+.\.venv-wheel-check\Scripts\python.exe -c "import pgzero, pgzrun; print(pgzero.__file__)"
+```
+
+**macOS / Linux:**
+
+```bash
+python3 -m venv .venv-wheel-check
+.venv-wheel-check/bin/python -m pip install dist/pgzero_plus-0.1.0-py3-none-any.whl
+.venv-wheel-check/bin/python -m pip check
+.venv-wheel-check/bin/python -c "import pgzero, pgzrun; print(pgzero.__file__)"
+```
+
+**Python 3.6 compatibility:** This fork targets Python 3.6 through 3.13, including older Codio environments. The modern build backend does not support building from source on Python 3.6. Before a release, install the **built wheel** in Codio and run a representative game there; passing tests on Python 3.13 does not establish compatibility with Python 3.6.
+
+## Publishing Releases
+
+GitHub Actions handles publishing through `.github/workflows/release.yml`. A new package is **not** published on every push to `main`; publishing starts only when you push a version tag.
+
+### One-time PyPI Setup
+
+1. Create a GitHub repository environment named `pypi` under **Settings → Environments**.
+2. Configure [PyPI Trusted Publishing](https://docs.pypi.org/trusted-publishers/) for project `pgzero-plus`, GitHub owner `mjdargen`, repository `pgzero`, workflow `release.yml`, and environment `pypi`. For a first release, use a _pending trusted publisher_ if the project has not yet been created on PyPI.
+
+This allows GitHub Actions to publish without storing a PyPI API token.
+
+### Create a Release
+
+1. Set the new `version` in `pyproject.toml`. For example, `version = "0.1.0"`.
+2. Commit and push your changes to `main`, then confirm that **Code Checks** passes on the [Actions page](https://github.com/mjdargen/pgzero/actions).
+3. Create and push a Git tag **matching** that version, with a leading `v`:
+
+```bash
+git switch main
+git pull
+git tag -a v0.1.0 -m "Release v0.1.0"
+git push origin v0.1.0
+```
+
+The release workflow verifies the version, runs the checks, builds the wheel and source archive, publishes to PyPI, and creates a GitHub Release with the built files attached. If a check or build fails, publishing stops.
+
+For a later release, update the version number and use its matching tag (for example, `0.1.1` and `v0.1.1`). Use patch releases for bug fixes and minor releases for new features. **PyPI does not allow replacing files for an existing published version.**
+
+## Credits & License
+
+This project is an independent fork of [Pygame Zero](https://github.com/lordmauve/pgzero), originally developed by Daniel Pope and contributors.
+
+Original documentation: https://pygame-zero.readthedocs.io/
+
+Licensed under the GNU Lesser General Public License v3.0 or later (LGPL-3.0-or-later).