SwirEngine 2.2.0
SwirEngine is a Python-first engine for complete 2D, 3D and multiplayer games. Version 2.2.0 extends the shipping runtime with production tools and visual creation workflows while preserving the published 2.1 compatibility baseline.
Included in 2.2
- runtime-backed material, shader, terrain, foliage, animation, particle/VFX and lighting tools;
- responsive UI authoring over the shipping retained UI toolkit;
- privacy-safe multiplayer diagnostics and capability-gated editor extensions;
- project-confined resources, deterministic serialization and relocated export validation;
- explicit 64-bit CPython 3.10–3.14 qualification on the maintained hosted-runner matrix.
The authoritative availability and source identity for this version are the package index metadata,
the immutable v2.2.0 tag and the corresponding GitHub Release provenance. Repository roadmaps
and transient candidate status do not override those public records.
Documentation, migration guidance and source are available from the SwirEngine repository.
1 maintainer
Metadata
1 maintainer
Release files for swirengine 2.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| swirengine-2.2.0.tar.gz | 2.9 MB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| swirengine-2.2.0-py3-none-any.whl | Python 3 | none | any | Details |
| swirengine-2.2.0-cp314-cp314-win_amd64.whl | CPython 3.14 | CPython 3.14 | Windows x86-64 | Details |
Total release size: 4.7 MB
Release files / swirengine-2.2.0.tar.gz
| Download URL | swirengine-2.2.0.tar.gz |
|---|---|
| Size | 2.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f2048d8d5332f449a90d41164b1d19521f2c5802a0b40b5d3d9d0370cc37053
|
|
BLAKE2b-256 checksum How to use checksums |
1c3dd4f3c0e3fea1c9022074d1d474234b80faf6fb9795fb431b4a04a57df4f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency logRelease files / swirengine-2.2.0-py3-none-any.whl
| Download URL | swirengine-2.2.0-py3-none-any.whl |
|---|---|
| Size | 827.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a16b47d9376e4fcf570ba91ce03545c62127999a61e6c60751a836f609bf4646
|
|
BLAKE2b-256 checksum How to use checksums |
498870dbc19ea94a1d64f70c57a1ec8908ee4ec7991e0ade719224e177bad430
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency logRelease files / swirengine-2.2.0-cp314-cp314-win_amd64.whl
| Download URL | swirengine-2.2.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 945.6 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
1261932138e183773f3131ca7972d442e667e1d56c944ed8d18f3fc023f0ac8d
|
|
BLAKE2b-256 checksum How to use checksums |
642da2f4830667b661b049358cd2d0a3c09e7ffdec0f3c778d738cefbea0a029
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency log
