This release is a pre-release and may not be stable for production use.
gym-breakout-pygame
Gym Breakout environment using Pygame.
Install
Install with pip:
pip3 install gym_breakout_pygame==0.0.1a2
Or, install from source:
git clone https://github.com/sapienza-rl/gym-breakout-pygame.git
cd gym-breakout-pygame
python3 setup.py install
Development
-
clone the repo:
git clone https://github.com/sapienza-rl/gym-breakout-pygame.git cd gym-breakout-pygame -
Create/activate the virtual environment:
pipenv shell -
Run a short demo:
python gym_breakout_pygame/breakout_env.py
You should get:
Tests
TODO
License
MIT License.
Credits
The code is largely inspired by RLGames
1 maintainer
Metadata
1 maintainer
Release files for gym-breakout-pygame 0.0.1a2
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 | |
|---|---|---|---|---|
| gym_breakout_pygame-0.0.1a2.tar.gz | 176.4 kB | Without provenance | Details |
Release files / gym_breakout_pygame-0.0.1a2.tar.gz
| Download URL | gym_breakout_pygame-0.0.1a2.tar.gz |
|---|---|
| Size | 176.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc83b9c5fa4f13181ef4190e20a0cb32a6a603c025858bbe5fb3ea85bb180d85
|
|
BLAKE2b-256 checksum How to use checksums |
65c1dca6a6a5d974784075c95c5ba5852b84fa0c35a61da5757e6336dce8a603
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.2
|
Security for gym-breakout-pygame 0.0.1a2
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.
