Setuptools plugin for Rust extensions

example workflow pypi package readthedocs code style: black

setuptools-rust is a plugin for setuptools to build Rust Python extensions implemented with PyO3 or rust-cpython.

Compile and distribute Python extensions written in Rust as easily as if they were written in C.


For a complete example, see html-py-ever.

First, you need to create a bunch of files:

from setuptools import setup
from setuptools_rust import Binding, RustExtension

    rust_extensions=[RustExtension("hello_rust.hello_rust", binding=Binding.PyO3)],
    # rust extensions are not zip safe, just like C-extensions.

For a complete reference of the options supported by the RustExtension class, see the API reference.

This file is required for building source distributions

include Cargo.toml
recursive-include src *


requires = ["setuptools", "wheel", "setuptools-rust"]

set -ex

curl -sSf | sh -s -- --default-toolchain stable -y
export PATH="$HOME/.cargo/bin:$PATH"

cd /io

for PYBIN in /opt/python/cp{35,36,37,38,39}*/bin; do
    "${PYBIN}/pip" install -U setuptools wheel setuptools-rust
    "${PYBIN}/python" bdist_wheel

for whl in dist/*.whl; do
    auditwheel repair "$whl" -w dist/


You can use same commands as for c-extensions. For example:

>>> python ./ develop
running develop
running egg_info
writing hello-rust.egg-info/PKG-INFO
writing top-level names to hello_rust.egg-info/top_level.txt
writing dependency_links to hello_rust.egg-info/dependency_links.txt
reading manifest file 'hello_rust.egg-info/SOURCES.txt'
writing manifest file 'hello_rust.egg-info/SOURCES.txt'
running build_ext
running build_rust
cargo build --manifest-path extensions/Cargo.toml --features python3
    Finished debug [unoptimized + debuginfo] target(s) in 0.0 secs

Creating /.../lib/python3.6/site-packages/hello_rust.egg-link (link to .)

Installed hello_rust
Processing dependencies for hello_rust==1.0
Finished processing dependencies for hello_rust==1.0

Or you can use commands like bdist_wheel (after installing wheel).

By default, develop will create a debug build, while install will create a release build.

Binary wheels on linux

To build binary wheels on linux, you need to use the manylinux docker container. You also need a similar to the one in the example, which will be run in that container.

First, pull the manylinux2014 Docker image:

docker pull

Then use the following command to build wheels for supported Python versions:

docker run --rm -v `pwd`:/io /io/

This will create wheels in the dist directory:

$ ls dist
hello_rust-0.1.0-cp35-cp35m-linux_x86_64.whl          hello_rust-0.1.0-cp35-cp35m-manylinux2014_x86_64.whl
hello_rust-0.1.0-cp36-cp36m-linux_x86_64.whl          hello_rust-0.1.0-cp36-cp36m-manylinux2014_x86_64.whl
hello_rust-0.1.0-cp37-cp37m-linux_x86_64.whl          hello_rust-0.1.0-cp37-cp37m-manylinux2014_x86_64.whl
hello_rust-0.1.0-cp38-cp38-linux_x86_64.whl           hello_rust-0.1.0-cp38-cp38-manylinux2014_x86_64.whl
hello_rust-0.1.0-cp39-cp39-linux_x86_64.whl           hello_rust-0.1.0-cp39-cp39-manylinux2014_x86_64.whl

You can then upload the manylinux2014 wheels to pypi using twine.

It is possible to use any of the manylinux docker images: manylinux1, manylinux2010 or manylinux2014. (Just replace manylinux2014 in the above instructions with the alternative version you wish to use.)

Binary wheels on macOS

For building wheels on macOS it is sufficient to run the bdist_wheel command, i.e. bdist_wheel.

To build universal2 wheels set the ARCHFLAGS environment variable to contain both x86_64 and arm64, for example ARCHFLAGS="-arch x86_64 -arch arm64". Wheel-building solutions such as ``cibuildwheel` <>`_ set this environment variable automatically.


  • build - Standard build command builds all rust extensions.

  • build_rust - Command builds all rust extensions.

  • clean - Standard clean command executes cargo clean for all rust extensions.

  • check - Standard check command executes cargo check for all rust extensions.

  • tomlgen_rust - Automatically generate a Cargo.toml manifest based on Python package metadata. See the example project on GitHub for more information about this command.