[](https://travis-ci.org/CTPUG/pygame_cffi)
[](https://pypi.python.org/pypi/pygame_cffi)
[](https://ci.appveyor.com/project/CTPUG/pygame-cffi/branch/master)
A cffi-based SDL wrapper that copies the pygame API.
We copy various code and API ideas from pygame, so we inherit pygame's
LGPL v2.1, or later license.
## Discussion
We have a Google Group: https://groups.google.com/forum/#!forum/pygame-cffi.
Any pygame-cffi discussion welcome!
There is also the #pygame-cffi channel on irc.freenode.net
## Installation
1. Install the requirements listed below. On a Debian-based system, all
requirements can be installed using `sudo apt-get build-dep pygame`
(pygame_cffi requires most of the pygame dependencies).
2. `pip install pygame_cffi`
## Requirements
pygame_cffi requires a recent version of python-cffi to build (at least
version 1.3.0).
* libjpeg-dev
* libpng-dev
* libsdl1.2-dev
* libsdl-image1.2-dev
* libsdl-mixer1.2-dev
* libsdl-ttf2.0-dev
## Local Development
1. Install dependencies (probably in a virtualenv)
2. Run `cffi_builders/build.py`
3. Hack
## Running Tests
* Upstream pygame unit tests: `python -m test`
* Tests that are known to fail on pygame_cffi are marked as expected
failures. To see these failures, pass the `--expected-failures`
argument.
* Conformance between pygame and pygame_cffi: See `conformance/README`
* pygame_cffi functionality example apps are in the `demos` directory
## Building on windows
To build on windows, you need to download the appropriate dependency libraries.
The ``pygame`` project provides all the required libraries in a nicely
bundled set, available from `https://bitbucket.org/llindstrom/pygame/downloads/`
For 32 bit machines, download the latest prebuilt-x86 zipfile and
unzip it under the pygame_cffi directory.
For 64 bit machines, download the latest prebuild-x64 zipfile and
unzip it under the pygame_cffi directory.
Then run python setup.py build to compile the modules.
Metadata
Release files for pygame_cffi 0.2.1
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 |
|---|---|---|---|---|
| pygame_cffi-0.2.1.tar.gz | 422.8 kB | Without provenance | Details for pygame_cffi-0.2.1.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| pygame_cffi-0.2.1-cp36-cp36m-win_amd64.whl | CPython 3.6 | CPython 3.6 pymalloc | Windows x86-64 | Details for pygame_cffi-0.2.1-cp36-cp36m-win_amd64.whl |
| pygame_cffi-0.2.1-cp36-cp36m-win32.whl | CPython 3.6 | CPython 3.6 pymalloc | Windows x86-32 | Details for pygame_cffi-0.2.1-cp36-cp36m-win32.whl |
| pygame_cffi-0.2.1-cp27-cp27m-win_amd64.whl | CPython 2.7 | CPython 2.7 pymalloc | Windows x86-64 | Details for pygame_cffi-0.2.1-cp27-cp27m-win_amd64.whl |
| pygame_cffi-0.2.1-cp27-cp27m-win32.whl | CPython 2.7 | CPython 2.7 pymalloc | Windows x86-32 | Details for pygame_cffi-0.2.1-cp27-cp27m-win32.whl |
Total release size: 9.3 MB
Release files / pygame_cffi-0.2.1.tar.gz
| Download URL | pygame_cffi-0.2.1.tar.gz |
|---|---|
| Size | 422.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e5c2914296c9ed970da464ce9f800aec7ef9fcad1e31e4204f0783a47b275ce5
|
|
BLAKE2b-256 checksum How to use checksums |
650a985730279c68db126d19aa6309573403fcd3700f83d3bbf9984302341b4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pygame_cffi-0.2.1-cp36-cp36m-win_amd64.whl
| Download URL | pygame_cffi-0.2.1-cp36-cp36m-win_amd64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.6 CPython 3.6 pymalloc Windows x86-64 |
|
SHA-256 checksum How to use checksums |
75304a0f319a568eae2cfddd986c46bba2562a37d3b4f8472db695531e969515
|
|
BLAKE2b-256 checksum How to use checksums |
90d351cf34d6389b03381e59f8090ce2a3280efdcb04d415156c5444029f0379
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pygame_cffi-0.2.1-cp36-cp36m-win32.whl
| Download URL | pygame_cffi-0.2.1-cp36-cp36m-win32.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.6 CPython 3.6 pymalloc Windows x86-32 |
|
SHA-256 checksum How to use checksums |
d24ef7d6ac45f184b357fca80f742d27edbcb3e9075063912d26e34d70504c14
|
|
BLAKE2b-256 checksum How to use checksums |
9d32bc63cc30fc6a5a0513fca729366a4b052987e64728b220813fecf2e11de1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pygame_cffi-0.2.1-cp27-cp27m-win_amd64.whl
| Download URL | pygame_cffi-0.2.1-cp27-cp27m-win_amd64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 2.7 CPython 2.7 pymalloc Windows x86-64 |
|
SHA-256 checksum How to use checksums |
4d2aa64a1862a72c08d4c0696d69e162c1d3bc7d421ed9b8570a01b651a61595
|
|
BLAKE2b-256 checksum How to use checksums |
d88d2893865a8a828fdefad064f4d4cbd0a1a0e293ff43f4818ccc03971bea3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pygame_cffi-0.2.1-cp27-cp27m-win32.whl
| Download URL | pygame_cffi-0.2.1-cp27-cp27m-win32.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 2.7 CPython 2.7 pymalloc Windows x86-32 |
|
SHA-256 checksum How to use checksums |
6ca3e071e7a3981c83fdb6ae1458f21ed8d1953bbc1d705191e75999aec3a30a
|
|
BLAKE2b-256 checksum How to use checksums |
db217979959920cc95706807d7fad91e609bd0894e8a4aa3553c8af6a40abfd3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pygame_cffi 0.2.1
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.