autopxd2
Automatically generate Cython .pxd declaration files from C/C++ header files.
Overview
autopxd2 parses C and C++ header files and generates Cython .pxd declaration files, enabling you to call native C/C++ libraries from Cython without manually writing boilerplate declarations.
Key features:
- Generates complete
.pxddeclaration files from C/C++ headers - Powered by
headerkit, with a choice of parser backends: LLVMlibclang(supporting LLVM 18–23) ortree-sitter(no system LLVM required) - Full C++ support: classes, methods, constructors, multiple inheritance, templates, and namespaces
- Automatic system include path detection
- Auto-generates
cimportstatements for standard library types and bundled stubs - Cross-platform support (Linux, macOS, Windows)
Supported Features
C Features
| Feature | Supported |
|---|---|
| Structs and unions | ✓ |
| Enums (with expressions) | ✓ |
| Typedefs | ✓ |
| Function declarations | ✓ |
| Function pointers | ✓ |
| Arrays (fixed and flexible) | ✓ |
| Pointers and const qualifiers | ✓ |
| Forward declarations | ✓ |
| Anonymous structs/unions | ✓ |
| Bit fields | ✓ |
#define macros (int, float, string) |
✓ |
| Circular type dependencies | ✓ |
C++ Features
| Feature | Supported |
|---|---|
Classes and structs (cppclass) |
✓ |
| Constructors | ✓ |
| Destructors | not emitted — Cython cppclass blocks do not declare them |
Methods (const, @staticmethod) |
✓ |
| Multiple inheritance | ✓ |
| Namespaces (including nested) | ✓ |
Generic function and method templates (T max[T](T a, T b)) |
✓ |
| Class templates with type parameters | ✓ |
| Template specializations | ✓ |
| Operator overloading (renamed for Cython) | ✓ |
| References and const references | ✓ |
Installation
pip install autopxd2
autopxd2 uses headerkit, which vendors official LLVM clang Python bindings for LLVM 18–23 directly. No separate clang or clang2 Python package is needed.
You only need the system libclang shared library (libclang.so, libclang.dylib, or libclang.dll).
If libclang is not already installed on your system, install it via your system package manager:
- macOS:
brew install llvm - Ubuntu/Debian:
sudo apt-get install libclang-dev - Fedora/RHEL:
sudo dnf install clang-devel - Windows:
winget install LLVM.LLVM
Or use HeaderKit's built-in installer:
python -m headerkit.install_libclang
See the installation docs for more details.
Alternative: Tree-sitter Backend (No LLVM Dependency)
To parse C and C++ headers without requiring system libclang, install the treesitter extra:
pip install "autopxd2[treesitter]"
Then specify --backend tree-sitter:
autopxd --backend tree-sitter myheader.h myheader.pxd
The tree-sitter backend parses the given file only. Compared to libclang it does not:
- follow
#includedirectives, so declarations from included headers are absent - extract
#definemacros as constants - detect system include paths
- accept
--stdor--clang-arg(both are rejected with an error)
Quick Start
# Generate a .pxd file from a C header
autopxd myheader.h myheader.pxd
# Parse a C++ header
autopxd --cpp myclass.hpp myclass.pxd
# Add project-specific include directories (system includes are auto-detected)
autopxd -I ./include myheader.h myheader.pxd
# Write to stdout (omit output file or use '-')
autopxd myheader.h > myheader.pxd
# Read from stdin
cat myheader.h | autopxd -
Usage
autopxd [OPTIONS] [INFILE] [OUTFILE]
Options:
-v, --version Print version and exit.
-b, --backend TEXT Parser backend (default: auto, using libclang).
--list-backends List available backends and exit.
--json JSON output (with --list-backends).
-q, --quiet Suppress warnings.
--debug / --no-debug Print debug info to stderr.
-I, --include-dir <dir> Add include search path.
-D, --define <macro> Define preprocessor macro.
--allowlist <pattern> Only emit declarations from files matching pattern.
--denylist <pattern> Never emit declarations from files matching pattern.
Wins over --allowlist.
-w, --whitelist <pattern> Deprecated alias for --allowlist.
-x, --cpp Parse as C++.
--std <std> Language standard (e.g., c11, c++17).
--clang-arg <arg> Pass argument to clang.
--no-default-includes Disable system include auto-detection.
-P, --project-prefix <path> Treat path as project (not system) for umbrella headers.
--no-recursive Disable recursive parsing of umbrella headers.
--max-depth <n> Max recursion depth for umbrella headers (default: 10).
-h, --help Show this message and exit.
By default, declarations from every non-system included header are emitted.
--no-recursive confines the output to the input header's own declarations.
--allowlist narrows the emitted set in either mode, and --denylist subtracts
from it; a file matching both lists is excluded, because deny wins over allow.
Automatic Imports
autopxd2 automatically generates cimport statements for commonly used types when using the libclang backend.
Cython Standard Library Types
When headers use types from C standard library headers, autopxd generates appropriate Cython cimports:
// input.h
#include <stdio.h>
#include <stdint.h>
uint32_t process(FILE *f);
# Generated output
from libc.stdint cimport uint32_t
from libc.stdio cimport FILE
cdef extern from "input.h":
uint32_t process(FILE* f)
Bundled Stub Types
For types not in Cython's standard library, autopxd provides bundled stub declarations:
// input.h
#include <stdarg.h>
void log_message(const char *fmt, va_list args);
# Generated output
from headerkit.stubs.stdarg cimport va_list
cdef extern from "input.h":
void log_message(const char* fmt, va_list args)
C++ STL Types
C++ standard library types are automatically imported from libcpp:
// input.hpp
#include <vector>
#include <string>
std::vector<std::string> get_items();
# Generated output
from libcpp.string cimport string
from libcpp.vector cimport vector
cdef extern from "input.hpp":
vector[string] get_items()
Documentation
Full documentation is available at elijahr.github.io/python-autopxd2.
Docker
A Docker image with libclang pre-installed is available:
docker run --rm -v $(pwd):/work -w /work ghcr.io/elijahr/python-autopxd2 autopxd myheader.h
See Docker Usage for more examples.
Contributing
Contributions are welcome. See CONTRIBUTING.md for development setup and guidelines.
License
MIT License. See LICENSE for details.
Acknowledgments
This project is a fork of python-autopxd by Thiago de Arruda.
Metadata
Release files for autopxd2 4.0.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 | |
|---|---|---|---|
| autopxd2-4.0.1.tar.gz | 95.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autopxd2-4.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 108.7 kB
Release files / autopxd2-4.0.1.tar.gz
| Download URL | autopxd2-4.0.1.tar.gz |
|---|---|
| Size | 95.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c7d565d7732c76fb632c6300daedf13f818d2343db809813a4d559cb15fbc4b
|
|
BLAKE2b-256 checksum How to use checksums |
dc129ba7b0adfdd9413575cf66ff8d93db265f9a217a503ab3db5ef43c67d110
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 19, 2026.
Transparency logRelease files / autopxd2-4.0.1-py3-none-any.whl
| Download URL | autopxd2-4.0.1-py3-none-any.whl |
|---|---|
| Size | 13.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
814020731d84cdd324fa66561d5c2ca12a10bf9ee5d9f472adbfdc41ab77e95c
|
|
BLAKE2b-256 checksum How to use checksums |
589d36fc8df198b856423b49718536e264ac294eaaf7e8b417d21bd48079d110
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 19, 2026.
Transparency log