Help with packaging a rust library for Python

Apparently there’s a markup language for recipes and an official parser that has bindings that I understand can be used to give access to the APIs in Python. I’m wondering if anyone here has experience with UniFFI and might be willing to help me understand what needs to be done to package it?

I’ve not come across UniFFI before - thanks. Is there a particular reason to use this instead of PyO3 and Maturin, e.g. supporting non-Python languages too?

The package in question isn’t something I’ve worked on so I have no say in their decision making process. Since they are exposing the bindings I would like to help them package it since I would like to use it for something myself.

I’ve had a pleasant experience with writing Python bindings for Rust with PyO3, maturin, and cibuildwheel. I would highly recommend trying out the very first example in PyO3 docs to get a feel for it.

1 Like

This is an existing package that has Python bindings. I want to help them package and distribute it.

Apparently the answer is that Maturin supports UniFFI bindings. From what I can tell I just need to add the pyproject.toml and configure it to use that as a backend.

3 Likes