cogames — retired
CoGames has been retired in favor of Coworld.
This package exists only as a tombstone for pip install cogames. It has no
runtime surface; importing it emits a DeprecationWarning.
Migration
| Old import | New import |
|---|---|
from cogames.core import … |
from mettagrid.cogame.core import … |
from cogames.game import … |
from mettagrid.cogame.game import … |
from cogames.variants import … |
from mettagrid.cogame.variants import … |
from cogames.sdk.cogsguard import … |
from mettagrid.sdk.cogsguard import … |
The cogames CLI (cogames play, cogames train, …), cogames.policy,
cogames.standalone_games, metta_alo, and the embedded game configs
(cogames.games.cogs_vs_clips, etc.) are not migrated; they were tied to
infrastructure that no longer exists. Use Coworld for an equivalent runtime.
Drop cogames from your dependencies.
Metadata
Release files for cogames 0.28.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 | Provenance | Actions |
|---|---|---|---|---|
| cogames-0.28.0.tar.gz | 3.2 kB | With provenance | Details for cogames-0.28.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cogames-0.28.0-py3-none-any.whl | Python 3 | none | any | Details for cogames-0.28.0-py3-none-any.whl |
Total release size: 6.2 kB
Release files / cogames-0.28.0.tar.gz
| Download URL | cogames-0.28.0.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b2c61d5c9b937f36259f32bc86fb9bf5576c60f3eba725a5741353434a26963
|
|
BLAKE2b-256 checksum How to use checksums |
c3dbd20496f522758abb8c46542e7ae95e9e495c4c6e24c53f09d2623987e830
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 30, 2026.
Transparency logRelease files / cogames-0.28.0-py3-none-any.whl
| Download URL | cogames-0.28.0-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fa0427e05dce62f7a44f22f75b30e892a0dc02b683202a9910cad1192a85f1d8
|
|
BLAKE2b-256 checksum How to use checksums |
3f14aad1fd6bd36e4a3e8b20b9ad95887cf9fd5fdac9f09adcc1172eeffb4fb7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 30, 2026.
Transparency logSecurity for cogames 0.28.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for cogames-0.28.0.tar.gz
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 May 30, 2026.
Transparency logA 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.