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

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.12,<0.13"]
build-backend = "maturin"

If a pyproject.toml with a [build-system] entry is present, maturin will build a source distribution of your package, unless --no-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.12,<0.13"]
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.12.18_beta.2.tar.gz (155.2 kB view details)

Uploaded Source

Built Distributions

maturin-0.12.18_beta.2-py3-none-win_arm64.whl (5.1 MB view details)

Uploaded Python 3 Windows ARM64

maturin-0.12.18_beta.2-py3-none-win_amd64.whl (5.9 MB view details)

Uploaded Python 3 Windows x86-64

maturin-0.12.18_beta.2-py3-none-win32.whl (5.4 MB view details)

Uploaded Python 3 Windows x86

maturin-0.12.18_beta.2-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl (9.8 MB view details)

Uploaded Python 3 manylinux: glibc 2.17+ s390x

maturin-0.12.18_beta.2-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.12.18_beta.2-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.musllinux_1_1_armv7l.whl (9.2 MB view details)

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

maturin-0.12.18_beta.2-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_1_aarch64.whl (9.2 MB view details)

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

maturin-0.12.18_beta.2-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.12.18_beta.2-py3-none-manylinux_2_12_i686.manylinux2010_i686.musllinux_1_1_i686.whl (9.7 MB view details)

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

maturin-0.12.18_beta.2-py3-none-macosx_10_9_x86_64.macosx_11_0_arm64.macosx_10_9_universal2.whl (12.9 MB view details)

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

maturin-0.12.18_beta.2-py3-none-macosx_10_7_x86_64.whl (6.7 MB view details)

Uploaded Python 3 macOS 10.7+ x86-64

File details

Details for the file maturin-0.12.18_beta.2.tar.gz.

File metadata

  • Download URL: maturin-0.12.18_beta.2.tar.gz
  • Upload date:
  • Size: 155.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: maturin/0.12.17

File hashes

Hashes for maturin-0.12.18_beta.2.tar.gz
Algorithm Hash digest
SHA256 fce78dd1ce758bd098cc98efc42338ba3f2f99db0bda5687adcbb24efcc3ceb9
MD5 1eba99dba1099da3bd9ee722dc3e02a6
BLAKE2b-256 851315d3762ef6b46a54f2ac38a24cffca9b924af7b55ef067802beffefe94e0

See more details on using hashes here.

File details

Details for the file maturin-0.12.18_beta.2-py3-none-win_arm64.whl.

File metadata

File hashes

Hashes for maturin-0.12.18_beta.2-py3-none-win_arm64.whl
Algorithm Hash digest
SHA256 7849174380a8de3719ddde7f779827027ac5dfd7d640b545ebd00f4f1ea41a89
MD5 5088637afa5d17497a516fec2495c5b3
BLAKE2b-256 7db1233052bff3ee3c503b459baa0b669e326420b41282d896b13426e665e42e

See more details on using hashes here.

File details

Details for the file maturin-0.12.18_beta.2-py3-none-win_amd64.whl.

File metadata

File hashes

Hashes for maturin-0.12.18_beta.2-py3-none-win_amd64.whl
Algorithm Hash digest
SHA256 110ba9cb4e27a8ec1ffbd4ef5e3543941a4643322808e7558c9ff39a48f7f3dc
MD5 ccd9fdb8fe6fb9bb7d3b87d13236fe91
BLAKE2b-256 43d69af960297aaf909314cbe4ba5adb8d4e3417a24a805163b5a353191579b0

See more details on using hashes here.

File details

Details for the file maturin-0.12.18_beta.2-py3-none-win32.whl.

File metadata

File hashes

Hashes for maturin-0.12.18_beta.2-py3-none-win32.whl
Algorithm Hash digest
SHA256 4c4acd5f0afaaf0932040af19fc00d498bb5d4de80f58a5c3474b81d5a8b0b3a
MD5 2f2a0ac49d91fca0294d20622e65968d
BLAKE2b-256 0d8decbc653ab52fb8dca399316a29beb421d534e1d3f04d147d15bf6cd3d87d

See more details on using hashes here.

File details

Details for the file maturin-0.12.18_beta.2-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl.

File metadata

File hashes

Hashes for maturin-0.12.18_beta.2-py3-none-manylinux_2_17_s390x.manylinux2014_s390x.whl
Algorithm Hash digest
SHA256 465856b8df6810dd377c3958078ccc11a2bb2e31fdad41eb48829f5f73578fd3
MD5 73e09c3cb4c69535e440a10a27a122eb
BLAKE2b-256 def17d1c14c10b9e067fe1172ad68e11b9e2982c47e5f069cc725d51aa1ae8d1

See more details on using hashes here.

File details

Details for the file maturin-0.12.18_beta.2-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.musllinux_1_1_ppc64le.whl.

File metadata

File hashes

Hashes for maturin-0.12.18_beta.2-py3-none-manylinux_2_17_ppc64le.manylinux2014_ppc64le.musllinux_1_1_ppc64le.whl
Algorithm Hash digest
SHA256 96e7a701e8e548fce0dff323176ea61178f69143335f230b7e1b00f67e89536b
MD5 1c56a7289972a42573712b7c6b271c4c
BLAKE2b-256 2c3afac19806cb1ee965d487c6229e2a81d1ba0800c01230a47a7b9bd72f50ca

See more details on using hashes here.

File details

Details for the file maturin-0.12.18_beta.2-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.musllinux_1_1_armv7l.whl.

File metadata

File hashes

Hashes for maturin-0.12.18_beta.2-py3-none-manylinux_2_17_armv7l.manylinux2014_armv7l.musllinux_1_1_armv7l.whl
Algorithm Hash digest
SHA256 73dbe9f96230cd0dba3ef94320c7a6c984a168ec8f91b4abb66ce4cb089f53b9
MD5 5dbf393b450dab495b4a8054b6ad6ce2
BLAKE2b-256 12e9c796ee8c5f4fb6d07d183423e2e286129898d84ca4681ae36e0a52df8789

See more details on using hashes here.

File details

Details for the file maturin-0.12.18_beta.2-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_1_aarch64.whl.

File metadata

File hashes

Hashes for maturin-0.12.18_beta.2-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.musllinux_1_1_aarch64.whl
Algorithm Hash digest
SHA256 42e9243002213df3bb6ac80d755ee1b7c22f47a2ea12ad316c7219419babeaf6
MD5 75114d0c56994cd8bd47159895860ea9
BLAKE2b-256 6bfd564d5259793e4d7e9faa5ee2a777fc24507f1ed4b51c90797582e0d19ec9

See more details on using hashes here.

File details

Details for the file maturin-0.12.18_beta.2-py3-none-manylinux_2_12_x86_64.manylinux2010_x86_64.musllinux_1_1_x86_64.whl.

File metadata

File hashes

Hashes for maturin-0.12.18_beta.2-py3-none-manylinux_2_12_x86_64.manylinux2010_x86_64.musllinux_1_1_x86_64.whl
Algorithm Hash digest
SHA256 9ada5f70cf1e630556afefe13b07ca211b0e29b2e2d3fd4a4236b1f3ad72efbb
MD5 f20e9ddbbcfd40fba6650ffbca93322c
BLAKE2b-256 27cc4a6b904cb4cfe5ab3ac81c056d44856adfcfd8e8e5de227845be5101231c

See more details on using hashes here.

File details

Details for the file maturin-0.12.18_beta.2-py3-none-manylinux_2_12_i686.manylinux2010_i686.musllinux_1_1_i686.whl.

File metadata

File hashes

Hashes for maturin-0.12.18_beta.2-py3-none-manylinux_2_12_i686.manylinux2010_i686.musllinux_1_1_i686.whl
Algorithm Hash digest
SHA256 c203c15d6e402e4789a8bdb1907a58b5bdc3ef3491d39b6add2ea3b2b6904838
MD5 98cf972b9203469b66791d1245eb2601
BLAKE2b-256 3537ecdb4d1542bfd7208127927849cb448ec0cca33623a68614886c510b0da2

See more details on using hashes here.

File details

Details for the file maturin-0.12.18_beta.2-py3-none-macosx_10_9_x86_64.macosx_11_0_arm64.macosx_10_9_universal2.whl.

File metadata

File hashes

Hashes for maturin-0.12.18_beta.2-py3-none-macosx_10_9_x86_64.macosx_11_0_arm64.macosx_10_9_universal2.whl
Algorithm Hash digest
SHA256 b19d63855135b1bb5f5c113b0be7dbcb325a327b2376f23e79c2b2fe15fce545
MD5 6d70744af64716a6e6befa7766885fbb
BLAKE2b-256 3bb509996164637e76be228d22b329be0c55f2558292f3f413e66ca425299b75

See more details on using hashes here.

File details

Details for the file maturin-0.12.18_beta.2-py3-none-macosx_10_7_x86_64.whl.

File metadata

File hashes

Hashes for maturin-0.12.18_beta.2-py3-none-macosx_10_7_x86_64.whl
Algorithm Hash digest
SHA256 8b145708e9accd5a2d46cc86f0e8c68b589a624a919edbfd188369367b022106
MD5 8ec2d1878bd18201731d75bf1794a27a
BLAKE2b-256 fbcef7e9e579013ca42f540fe15b2002f80b7faeb5a32e9802a45f34fe55ceb3

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