Skip to main content
yace

Welcome to yace

PyPI Build Status https://coveralls.io/repos/github/safl/yace/badge.svg?branch=main pre-commit REUSE status

yace generates the bindings of a C API for other languages. You describe the FFI boundary of the API as a C header, in a subset of C99 that can be described equivalently in C, C++, Python, Rust and Zig, and yace generates, for each, code that is idiomatic for that language: for C, a C API with pretty-printers for every struct, union and enum. A field of bits, an integer whose parts are named by masks, is printed part by part, and read and written by part in every language. Headers outside the subset are parsed too, with every place they step outside it reported.

The project is hosted on GitHub, and its documentation is at safl.dk/yace.

Bindings are generated for C, C++, Python (ctypes), Cython (a compiled module, and a .pxd of the C API), Rust, Zig and Go. Each target builds and runs a check of what it generated against the layout the C compiler gives every record, and the C API and Zig check every function’s signature against the header too.

A header can also be written by a generator, from something other than C, and taken as one written by hand: yace --generate file.py:Class, or a generator installed by name. A generator proposed to xNVMe writes the NVMe specification headers of xNVMe in this way, from the data model that senfd makes of the specification documents.

Contributions are welcome; the documentation says how the code is laid out.

Metadata

Release files for yace 0.14.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for yace 0.14.0
File Size Uploaded Provenance Actions
yace-0.14.0.tar.gz 311.8 kB Without provenance Details for yace-0.14.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for yace 0.14.0
File Interpreter ABI Platform Actions
yace-0.14.0-py3-none-any.whl Python 3 none any Details for yace-0.14.0-py3-none-any.whl

Total release size: 552.7 kB

Release files / yace-0.14.0.tar.gz

Download URL yace-0.14.0.tar.gz
Size 311.8 kB
Tags Source
SHA-256 checksum
How to use checksums
789d11f045f17fa0b53a8da399132a52c56aa52423a30950ea1df6c307272871
BLAKE2b-256 checksum
How to use checksums
c169507d0d17a18558a654d04a1c3048ac045aeb2d918b1653df099df986e22c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Release files / yace-0.14.0-py3-none-any.whl

Download URL yace-0.14.0-py3-none-any.whl
Size 240.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
275345c3e21c6f3ebc3a6eec16d1446627fc9be27b0ab5c80656f2e0fb2106bc
BLAKE2b-256 checksum
How to use checksums
08091d876fe5e33044a043cc5302738fda0761091718d85fcaf30169846db019
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Security for yace 0.14.0

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.

Release history Release notifications | RSS feed

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page