pangocffi
Deprecation Notice: pangocffi is no longer being maintained. There are no plans to officially handover ownership of the project to another maintainer. PyGObject can be used as a replacement, but will also require migrating from cairocffi to pycairo. For more information, please see the PyGObject Migration Guide.
pangocffi is a CFFI-based set of Python bindings for pango.
pangocffi on its own is not that useful, since it depends on a PangoFontMap being declared against the PangoContext. PangoFontMap instances can easily be retrieved from libraries such as PangoCairo, PangoXft, PangoFT2, and PangoWin32 (See gnome's documentation 'Rendering with Pango' for a list of rendering engines).
See pangocairocffi for bindings that allow you to render pango objects with cairo.
The bindings are currently not fully implemented. Feel free to make a pull request to contribute!
Installation and usage
See 'Overview' for information on how to install the necessary libraries.
See 'Python API Reference' for additional information on all the objects.
Contributing
If you would like to contribute to this project, either by leaving feedback or submitting a pull request, please read 'CONTRIBUTING.md'.
1 maintainer
Metadata
1 maintainer
Release files for pangocffi 0.14.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 | |
|---|---|---|---|
| pangocffi-0.14.1.tar.gz | 47.7 kB | Details |
Release files / pangocffi-0.14.1.tar.gz
| Download URL | pangocffi-0.14.1.tar.gz |
|---|---|
| Size | 47.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
843a3ecad3c78e5950c32e7e87c9662849d4d2906045b1c87bb6380df028a3ff
|
|
BLAKE2b-256 checksum How to use checksums |
c15bb1ac67cb494366d3416172dfde4940e5898816165d84db74175d67097e46
|
| 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 Jun 28, 2026.
Transparency log
