PyClibrary

.. image:: https://github.com/MatthieuDartiailh/pyclibrary/workflows/Continuous%20Integration/badge.svg :target: https://github.com/MatthieuDartiailh/pyclibrary/actions .. image:: https://github.com/MatthieuDartiailh/pyclibrary/workflows/Documentation%20building/badge.svg :target: https://github.com/MatthieuDartiailh/pyclibrary/actions .. image:: https://codecov.io/gh/MatthieuDartiailh/pyclibrary/branch/master/graph/badge.svg :target: https://codecov.io/gh/MatthieuDartiailh/pyclibrary .. image:: https://readthedocs.org/projects/pyclibrary/badge/?version=latest :target: https://pyclibrary.readthedocs.io/en/latest/?badge=latest :alt: Documentation Status .. image:: https://badge.fury.io/py/pyclibrary.svg :target: https://badge.fury.io/py/pyclibrary :alt: Latest Version .. image:: https://img.shields.io/pypi/pyversions/pyclibrary.svg :target: https://badge.fury.io/py/pyclibrary :alt: Supported Python versions .. image:: https://img.shields.io/pypi/wheel/pyclibrary.svg :target: https://badge.fury.io/py/pyclibrary :alt: Wheel Status .. image:: https://img.shields.io/pypi/l/pyclibrary.svg :target: https://badge.fury.io/py/pyclibrary :alt: License

C parser and bindings automation for Python.

Fork of https://launchpad.net/pyclibrary.

PyCLibrary includes 1) a pure-python C parser and 2) an automation library that uses C header file definitions to simplify the use of c bindings. The C parser currently processes all macros, typedefs, structs, unions, enums, function prototypes, and global variable declarations, and can evaluate typedefs down to their fundamental C types + pointers/arrays/function signatures. Pyclibrary can automatically build c structs/unions and perform type conversions when calling functions via cdll/windll.

PyCLibrary tries to present a ffi agnostic API to allow using different bindings. For the time being only the ctypes based backend is implemented but a cffi backend should be possible to implement (the rational for it would be that the CParser can be used on raw header files which are not always well supported by the cffi parser).

However if you need to manipulate the C object coming back from the library which cannot simply be mapped to Python object your code will most likely not be backend independent so it is discouraged to try to switch between backends.