Skip to main content

Build and publish crates with pyo3, rust-cpython and cffi bindings as well as rust binaries as python packages

Project description

Maturin

formerly pyo3-pack

Actions Status FreeBSD Crates.io PyPI Maturin User Guide Chat on Gitter

Build and publish crates with pyo3, rust-cpython and cffi bindings as well as rust binaries as python packages.

This project is meant as a zero configuration replacement for setuptools-rust and milksnake. It supports building wheels for python 3.5+ on windows, linux, mac and freebsd, can upload them to pypi and has basic pypy support.

Check out the User Guide!

Usage

You can either download binaries from the latest release or install it with pip:

pip install maturin

There are four main commands:

  • maturin new creates a new cargo project with maturin configured.
  • maturin publish builds the crate into python packages and publishes them to pypi.
  • maturin build builds the wheels and stores them in a folder (target/wheels by default), but doesn't upload them. It's possible to upload those with twine or maturin upload.
  • maturin develop builds the crate and installs it as a python module directly in the current virtualenv. Note that while maturin develop is faster, it doesn't support all the feature that running pip install after maturin build supports.

pyo3 and rust-cpython bindings are automatically detected, for cffi or binaries you need to pass -b cffi or -b bin. maturin doesn't need extra configuration files and doesn't clash with an existing setuptools-rust or milksnake configuration. You can even integrate it with testing tools such as tox. There are examples for the different bindings in the test-crates folder.

The name of the package will be the name of the cargo project, i.e. the name field in the [package] section of Cargo.toml. The name of the module, which you are using when importing, will be the name value in the [lib] section (which defaults to the name of the package). For binaries, it's simply the name of the binary generated by cargo.

Python packaging basics

Python packages come in two formats: A built form called wheel and source distributions (sdist), both of which are archives. A wheel can be compatible with any python version, interpreter (cpython and pypy, mainly), operating system and hardware architecture (for pure python wheels), can be limited to a specific platform and architecture (e.g. when using ctypes or cffi) or to a specific python interpreter and version on a specific architecture and operating system (e.g. with pyo3 and rust-cpython).

When using pip install on a package, pip tries to find a matching wheel and install that. If it doesn't find one, it downloads the source distribution and builds a wheel for the current platform, which requires the right compilers to be installed. Installing a wheel is much faster than installing a source distribution as building wheels is generally slow.

When you publish a package to be installable with pip install, you upload it to pypi, the official package repository. For testing, you can use test pypi instead, which you can use with pip install --index-url https://test.pypi.org/simple/. Note that for publishing for linux, you need to use the manylinux docker container, while for publishing from your repository you can use the messense/maturin-action github action.

pyo3 and rust-cpython

For pyo3 and rust-cpython, maturin can only build packages for installed python versions. On linux and mac, all python versions in PATH are used. If you don't set your own interpreters with -i, a heuristic is used to search for python installations. On windows all versions from the python launcher (which is installed by default by the python.org installer) and all conda environments except base are used. You can check which versions are picked up with the list-python subcommand.

pyo3 will set the used python interpreter in the environment variable PYTHON_SYS_EXECUTABLE, which can be used from custom build scripts. Maturin can build and upload wheels for pypy with pyo3, even though only pypy3.7-7.3 on linux is tested.

Cffi

Cffi wheels are compatible with all python versions including pypy. If cffi isn't installed and python is running inside a virtualenv, maturin will install it, otherwise you have to install it yourself (pip install cffi).

maturin uses cbindgen to generate a header file, which can be customized by configuring cbindgen through a cbindgen.toml file inside your project root. Alternatively you can use a build script that writes a header file to $PROJECT_ROOT/target/header.h.

Based on the header file maturin generates a module which exports an ffi and a lib object.

Example of a custom build script
use cbindgen;
use std::env;
use std::path::Path;

fn main() {
    let crate_dir = env::var("CARGO_MANIFEST_DIR").unwrap();

    let bindings = cbindgen::Builder::new()
        .with_no_includes()
        .with_language(cbindgen::Language::C)
        .with_crate(crate_dir)
        .generate()
        .unwrap();
    bindings.write_to_file(Path::new("target").join("header.h"));
}

Mixed rust/python projects

To create a mixed rust/python project, create a folder with your module name (i.e. lib.name in Cargo.toml) next to your Cargo.toml and add your python sources there:

my-project
├── Cargo.toml
├── my_project
│   ├── __init__.py
│   └── bar.py
├── pyproject.toml
├── Readme.md
└── src
    └── lib.rs

You can specify a different python source directory in Cargo.toml by setting package.metadata.maturin.python-source, for example

[package.metadata.maturin]
python-source = "python"

then the project structure would look like this:

my-project
├── Cargo.toml
├── python
│   └── my_project
│       ├── __init__.py
│       └── bar.py
├── pyproject.toml
├── Readme.md
└── src
    └── lib.rs

Note This structure is recommended to avoid a common ImportError pitfall

maturin will add the native extension as a module in your python folder. When using develop, maturin will copy the native library and for cffi also the glue code to your python folder. You should add those files to your gitignore.

With cffi you can do from .my_project import lib and then use lib.my_native_function, with pyo3/rust-cpython you can directly from .my_project import my_native_function.

Example layout with pyo3 after maturin develop:

my-project
├── Cargo.toml
├── my_project
│   ├── __init__.py
│   ├── bar.py
│   └── my_project.cpython-36m-x86_64-linux-gnu.so
├── Readme.md
└── src
    └── lib.rs

Python metadata

maturin supports PEP 621, you can specify python package metadata in pyproject.toml. maturin merges metadata from Cargo.toml and pyproject.toml, pyproject.toml take precedence over Cargo.toml.

To specify python dependencies, add a list dependencies in a [project] section in the pyproject.toml. This list is equivalent to install_requires in setuptools:

[project]
name = "my-project"
dependencies = ["flask~=1.1.0", "toml==0.10.0"]

Pip allows adding so called console scripts, which are shell commands that execute some function in you program. You can add console scripts in a section [project.scripts]. The keys are the script names while the values are the path to the function in the format some.module.path:class.function, where the class part is optional. The function is called with no arguments. Example:

[project.scripts]
get_42 = "my_project:DummyClass.get_42"

You can also specify trove classifiers in your Cargo.toml under project.classifiers:

[project]
name = "my-project"
classifiers = ["Programming Language :: Python"]

Source distribution

maturin supports building through pyproject.toml. To use it, create a pyproject.toml next to your Cargo.toml with the following content:

[build-system]
requires = ["maturin>=0.13,<0.14"]
build-backend = "maturin"

If a pyproject.toml with a [build-system] entry is present, maturin can build a source distribution of your package when --sdist is specified. The source distribution will contain the same files as cargo package. To only build a source distribution, pass --interpreter without any values.

You can then e.g. install your package with pip install .. With pip install . -v you can see the output of cargo and maturin.

You can use the options compatibility, skip-auditwheel, bindings, strip, cargo-extra-args and rustc-extra-args under [tool.maturin] the same way you would when running maturin directly. The bindings key is required for cffi and bin projects as those can't be automatically detected. Currently, all builds are in release mode (see this thread for details).

For a non-manylinux build with cffi bindings you could use the following:

[build-system]
requires = ["maturin>=0.13,<0.14"]
build-backend = "maturin"

[tool.maturin]
bindings = "cffi"
compatibility = "linux"

manylinux option is also accepted as an alias of compatibility for backward compatibility with old version of maturin.

To include arbitrary files in the sdist for use during compilation specify sdist-include as an array of globs:

[tool.maturin]
sdist-include = ["path/**/*"]

There's a maturin sdist command for only building a source distribution as workaround for pypa/pip#6041.

Manylinux and auditwheel

For portability reasons, native python modules on linux must only dynamically link a set of very few libraries which are installed basically everywhere, hence the name manylinux. The pypa offers special docker images and a tool called auditwheel to ensure compliance with the manylinux rules. If you want to publish widely usable wheels for linux pypi, you need to use a manylinux docker image.

The Rust compiler since version 1.47 requires at least glibc 2.11, so you need to use at least manylinux2010. For publishing, we recommend enforcing the same manylinux version as the image with the manylinux flag, e.g. use --manylinux 2014 if you are building in quay.io/pypa/manylinux2014_x86_64. The messense/maturin-action github action already takes care of this if you set e.g. manylinux: 2014.

maturin contains a reimplementation of auditwheel automatically checks the generated library and gives the wheel the proper. If your system's glibc is too new or you link other shared libraries, it will assign the linux tag. You can also manually disable those checks and directly use native linux target with --manylinux off.

For full manylinux compliance you need to compile in a CentOS docker container. The pyo3/maturin image is based on the manylinux2010 image, and passes arguments to the maturin binary. You can use it like this:

docker run --rm -v $(pwd):/io ghcr.io/pyo3/maturin build --release  # or other maturin arguments

Note that this image is very basic and only contains python, maturin and stable rust. If you need additional tools, you can run commands inside the manylinux container. See konstin/complex-manylinux-maturin-docker for a small educational example or nanoporetech/fast-ctc-decode for a real world setup.

maturin itself is manylinux compliant when compiled for the musl target.

Code

The main part is the maturin library, which is completely documented and should be well integrable. The accompanying main.rs takes care username and password for the pypi upload and otherwise calls into the library.

The sysconfig folder contains the output of python -m sysconfig for different python versions and platform, which is helpful during development.

You need to install cffi and virtualenv (pip install cffi virtualenv) to run the tests.

There are some optional hacks that can speed up the tests (over 80s to 17s on my machine).

  1. By running cargo build --release --manifest-path test-crates/cargo-mock/Cargo.toml you can activate a cargo cache avoiding to rebuild the pyo3 test crates with every python version.
  2. Delete target/test-cache to clear the cache (e.g. after changing a test crate) or remove test-crates/cargo-mock/target/release/cargo to deactivate it.
  3. By running the tests with the faster-tests feature, binaries are stripped and wheels are only stored and not compressed.

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

maturin-0.13.0_beta.8.tar.gz (142.6 kB view details)

Uploaded Source

Built Distributions

maturin-0.13.0_beta.8-py3-none-win_arm64.whl (5.2 MB view details)

Uploaded Python 3 Windows ARM64

maturin-0.13.0_beta.8-py3-none-win_amd64.whl (6.0 MB view details)

Uploaded Python 3 Windows x86-64

maturin-0.13.0_beta.8-py3-none-win32.whl (5.5 MB view details)

Uploaded Python 3 Windows x86

maturin-0.13.0_beta.8-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl (9.8 MB view details)

Uploaded Python 3 manylinux: glibc 2.17+ s390x

maturin-0.13.0_beta.8-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.musllinux_1_1_ppc64le.whl (8.3 MB view details)

Uploaded Python 3 manylinux: glibc 2.17+ ppc64le musllinux: musl 1.1+ ppc64le

maturin-0.13.0_beta.8-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.musllinux_1_1_armv7l.whl (9.3 MB view details)

Uploaded Python 3 manylinux: glibc 2.17+ ARMv7l musllinux: musl 1.1+ ARMv7l

maturin-0.13.0_beta.8-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_1_aarch64.whl (9.3 MB view details)

Uploaded Python 3 manylinux: glibc 2.17+ ARM64 musllinux: musl 1.1+ ARM64

maturin-0.13.0_beta.8-py3-none-manylinux_2_12_x86_64.manylinux2010_x86_64.musllinux_1_1_x86_64.whl (9.6 MB view details)

Uploaded Python 3 manylinux: glibc 2.12+ x86-64 musllinux: musl 1.1+ x86-64

maturin-0.13.0_beta.8-py3-none-manylinux_2_12_i686.manylinux2010_i686.musllinux_1_1_i686.whl (9.8 MB view details)

Uploaded Python 3 manylinux: glibc 2.12+ i686 musllinux: musl 1.1+ i686

maturin-0.13.0_beta.8-py3-none-macosx_10_9_x86_64.macosx_11_0_arm64.macosx_10_9_universal2.whl (13.1 MB view details)

Uploaded Python 3 macOS 10.9+ universal2 (ARM64, x86-64) macOS 10.9+ x86-64 macOS 11.0+ ARM64

maturin-0.13.0_beta.8-py3-none-macosx_10_7_x86_64.whl (6.8 MB view details)

Uploaded Python 3 macOS 10.7+ x86-64

File details

Details for the file maturin-0.13.0_beta.8.tar.gz.

File metadata

  • Download URL: maturin-0.13.0_beta.8.tar.gz
  • Upload date:
  • Size: 142.6 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: maturin/0.12.20

File hashes

Hashes for maturin-0.13.0_beta.8.tar.gz
Algorithm Hash digest
SHA256 89104af09c486efb9e46fe75597a0b485c1ef201c00a8a87f34d7090a9a81068
MD5 2e7296dd4c1db8b4f68485591d285641
BLAKE2b-256 06bd4f5734617a1c27b6c36982ec52b5e708e20e653615329f7c81a3d3cd300e

See more details on using hashes here.

File details

Details for the file maturin-0.13.0_beta.8-py3-none-win_arm64.whl.

File metadata

File hashes

Hashes for maturin-0.13.0_beta.8-py3-none-win_arm64.whl
Algorithm Hash digest
SHA256 bfb4b2e9dae0e34ca2e54a9641bf36ff26912e393ebe3f7bc2b5598f06bd037d
MD5 22182f461cef1e2130fbcc79c8167001
BLAKE2b-256 7f9d55b36eeb1cdd27741565708a9aff48d500e70f393716adc075c8b2ce3f93

See more details on using hashes here.

File details

Details for the file maturin-0.13.0_beta.8-py3-none-win_amd64.whl.

File metadata

File hashes

Hashes for maturin-0.13.0_beta.8-py3-none-win_amd64.whl
Algorithm Hash digest
SHA256 02f1d79cf5eb867f698969dca9e10d632e74277b08ba5dc8664f285eb907a0bd
MD5 eb30d3fafe961be09e4b7cf2cf441b12
BLAKE2b-256 c8c1f08cf35c2b52c7e781b3e9d3c06ac9dd0da592c2b6324937b49d45190959

See more details on using hashes here.

File details

Details for the file maturin-0.13.0_beta.8-py3-none-win32.whl.

File metadata

File hashes

Hashes for maturin-0.13.0_beta.8-py3-none-win32.whl
Algorithm Hash digest
SHA256 33f7a86c23667a19440a82f1ceaf8c22876c9d10b9bbc22e87cbbd8aca9f7025
MD5 09539b08791ce4a56728e2aba45bb0a0
BLAKE2b-256 f61ffbb64950450875b2b7d15d79b70acf0024dc6f9ea1eacb8e3188368544f8

See more details on using hashes here.

File details

Details for the file maturin-0.13.0_beta.8-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl.

File metadata

File hashes

Hashes for maturin-0.13.0_beta.8-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl
Algorithm Hash digest
SHA256 a1bb6cc8d9cd96181bd836e0269b0b84c89d7cfdb4d2093d66ace87ca242b0d2
MD5 d36a2bbfbb46b786b2a187976448be37
BLAKE2b-256 e5359cdd080803e4a4c33e633e72bff191e2eb38ad1c346d937ec8c09697286c

See more details on using hashes here.

File details

Details for the file maturin-0.13.0_beta.8-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.musllinux_1_1_ppc64le.whl.

File metadata

File hashes

Hashes for maturin-0.13.0_beta.8-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.musllinux_1_1_ppc64le.whl
Algorithm Hash digest
SHA256 3e89e1b1a62465babba09cfed02f750ffae32fe2b4cccd321e6e6f68e9b94376
MD5 9627c56f30c7b3611b3ba07c09681c04
BLAKE2b-256 cb4365c9984fa78e572e6038b58e50bf14eaaf8fba82d1098e1dbe2640a07a8c

See more details on using hashes here.

File details

Details for the file maturin-0.13.0_beta.8-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.musllinux_1_1_armv7l.whl.

File metadata

File hashes

Hashes for maturin-0.13.0_beta.8-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.musllinux_1_1_armv7l.whl
Algorithm Hash digest
SHA256 212d1c7e48227c7cf9502bdaebe39ca660e800bfd5a33d6ed285b68fd95fb82e
MD5 6fb6a6751208ca431cba887701b09324
BLAKE2b-256 90a1c9f54500f8382fa097d7b390504834d55359f1d6bd96188f46c0883fda8c

See more details on using hashes here.

File details

Details for the file maturin-0.13.0_beta.8-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_1_aarch64.whl.

File metadata

File hashes

Hashes for maturin-0.13.0_beta.8-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_1_aarch64.whl
Algorithm Hash digest
SHA256 3c9de71e682bc43ed1f801a954db2b1d351c295541d65e59655df9669ac815aa
MD5 368b9bd521c4b0a92c94d08b782afd18
BLAKE2b-256 8922754be28888a1707bcac71d661fa40f4a019f2a842863df4289d25bc87fa6

See more details on using hashes here.

File details

Details for the file maturin-0.13.0_beta.8-py3-none-manylinux_2_12_x86_64.manylinux2010_x86_64.musllinux_1_1_x86_64.whl.

File metadata

File hashes

Hashes for maturin-0.13.0_beta.8-py3-none-manylinux_2_12_x86_64.manylinux2010_x86_64.musllinux_1_1_x86_64.whl
Algorithm Hash digest
SHA256 82fd6ad430f99bd56f2e96e31fe4555e020019b6ead0e242d3c6878f814c4815
MD5 089dafdea85afb0be40f99622a1c2e5c
BLAKE2b-256 d321f5b4016baebdad0ba83587cf92a7be73fd97de2055dd1619c83913a37225

See more details on using hashes here.

File details

Details for the file maturin-0.13.0_beta.8-py3-none-manylinux_2_12_i686.manylinux2010_i686.musllinux_1_1_i686.whl.

File metadata

File hashes

Hashes for maturin-0.13.0_beta.8-py3-none-manylinux_2_12_i686.manylinux2010_i686.musllinux_1_1_i686.whl
Algorithm Hash digest
SHA256 e3a95f6b7eaff2906bb9215a8cf3c865b4bc281a27222b7cc220b4d919353f6e
MD5 58b74faeaf0f65ce4aff06eb2337e01d
BLAKE2b-256 65c0bfd8b15449990955965213fbd169369dd4f17903805fa72d403b23f215e6

See more details on using hashes here.

File details

Details for the file maturin-0.13.0_beta.8-py3-none-macosx_10_9_x86_64.macosx_11_0_arm64.macosx_10_9_universal2.whl.

File metadata

File hashes

Hashes for maturin-0.13.0_beta.8-py3-none-macosx_10_9_x86_64.macosx_11_0_arm64.macosx_10_9_universal2.whl
Algorithm Hash digest
SHA256 a757adf8df6331bfd1efd52004baa52b2d394930ca256d23c6f3776bc525e69e
MD5 3ee05d412040289ca50f951785e74d11
BLAKE2b-256 ac3a71587cbfed6587d088858bde05666c715e9a947fdf47b38baf2461744307

See more details on using hashes here.

File details

Details for the file maturin-0.13.0_beta.8-py3-none-macosx_10_7_x86_64.whl.

File metadata

File hashes

Hashes for maturin-0.13.0_beta.8-py3-none-macosx_10_7_x86_64.whl
Algorithm Hash digest
SHA256 e493360e91bd7f8c60a3f5feeb9ed9776add5eae6f660d55c9003c51b73c8a2f
MD5 7f6cbd6c552d7ab765825c570fc3f317
BLAKE2b-256 97f1a2e96729971ef2c958f27646c65b07df282568fdcc2fce047c2b6a9d12fb

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page