cibuildwheel

Python wheels are great. Building them across Mac, Linux, Windows, on multiple versions of Python, is not.

cibuildwheel is here to help. cibuildwheel runs on your CI server - currently it supports Travis CI and Appveyor - and it builds and tests your wheels across all of your platforms.

cibuildwheel is in beta. It's brand new - I'd love for you to try it and help make it better!

What does it do?

	macOS 10.6+	manylinux i686	manylinux x86_64	Windows 32bit	Windows 64bit
Python 2.7	✅	✅	✅	✅	✅
Python 3.3		✅	✅	✅	✅
Python 3.4	✅	✅	✅	✅	✅
Python 3.5	✅	✅	✅	✅	✅
Python 3.6	✅	✅	✅	✅	✅

• Builds manylinux, macOS and Windows (32 and 64bit) wheels using Travis CI and Appveyor
• Bundles shared library dependencies on Linux and macOS through auditwheel and delocate
• Runs the library test suite against the wheel-installed version of your library

Usage

cibuildwheel currently works on Travis CI to build Linux and Mac wheels, and Appveyor to build Windows wheels.

cibuildwheel is not intended to run on your development machine. It will try to install packages globally; this is no good. Travis CI and Appveyor run their builds in isolated environments, so are ideal for this kind of script.

Minimal setup

• Create a .travis.yml file in your repo.

  matrix:
    include:
      - sudo: required
        services:
          - docker
      - os: osx
  
  script:
    - pip install cibuildwheel==0.4.0
    - cibuildwheel --output-dir wheelhouse
  

  Then setup a deployment method by following the Travis CI deployment docs, or see Delivering to PyPI below.

• Create an appveyor.yml file in your repo.

  build_script:
    - pip install cibuildwheel==0.4.0
    - cibuildwheel --output-dir wheelhouse
  artifacts:
    - path: "wheelhouse\\*.whl"
      name: Wheels
  

  Appveyor will store the built wheels for you - you can access them from the project console. Alternatively, you may want to store them in the same place as the Travis CI build. See Appveyor deployment docs for more info, or see Delivering to PyPI below.

• Commit those files, enable building of your repo on Travis CI and Appveyor, and push.

All being well, you should get wheels delivered to you in a few minutes.

⚠️ Got an error? Check the checklist below.

Options

usage: cibuildwheel [-h]
                    [--output-dir OUTPUT_DIR]
                    [--platform PLATFORM]
                    [project_dir]
    
Build wheels for all the platforms.

positional arguments:
  project_dir           Path to the project that you want wheels for.
                        Default: the current directory.

optional arguments:
  -h, --help            show this help message and exit
  --platform {auto,linux,macos,windows}
                        Platform to build for. For "linux" you need docker
                        running, on Mac or Linux. For "macos", you need a Mac
                        machine, and note that this script is going to
                        automatically install MacPython on your system, so
                        don't run on your development machine. For "windows",
                        you need to run in Windows, and it will build and test
                        for all versions of Python at C:\PythonXX[-x64].
  --output-dir OUTPUT_DIR
                        Destination folder for the wheels. 

Most of the config is via environment variables. These go into .travis.yml and appveyor.yml nicely.

Environment variable: CIBW_PLATFORM	Command line argument: --platform

Options: auto linux macos windows

Default: auto

auto will auto-detect platform using environment variables, such as TRAVIS_OS_NAME/APPVEYOR.

For linux you need Docker running, on Mac or Linux. For macos, you need a Mac machine, and note that this script is going to automatically install MacPython on your system, so don't run on your development machine. For windows, you need to run in Windows, and it will build and test for all versions of Python at C:\PythonXX[-x64].

Environment variable: CIBW_TEST_COMMAND

Optional.

Shell command to run the tests. The project root should be included in the command as "{project}". The wheel will be installed automatically and available for import from the tests.

Example: nosetests {project}/tests

Environment variable: CIBW_TEST_REQUIRES

Optional.

Space-separated list of dependencies required for running the tests.

Example: pytest
Example: nose==1.3.7 moto==0.4.31

Environment variable: CIBW_BEFORE_BUILD

Optional.

Shell command to run before building the wheel. This option allows you to run a command in each Python environment before the pip wheel command. This is useful if you need to set up some dependency so it's available during the build.

If dependencies are required to build your wheel (for example if you include a header from a Python module), set this to {pip} install ., and the dependencies will be installed automatically by pip. However, this means your package will be built twice - if your package takes a long time to build, you might wish to manually list the dependencies here instead.

The active Python binary can be accessed using {python}, and pip with {pip}. These are useful when you need to write python3 or pip3 on a Python 3.x build.

Example: {pip} install .
Example: {pip} install pybind11

Platform-specific variants also available:
CIBW_BEFORE_BUILD_MACOS | CIBW_BEFORE_BUILD_WINDOWS | CIBW_BEFORE_BUILD_LINUX

Environment variable: CIBW_SKIP

Optional.

Space-separated list of builds to skip. Each build has an identifier like cp27-manylinux1_x86_64 or cp34-macosx_10_6_intel - you can list ones to skip here and cibuildwheel won't try to build them.

The format is python_tag-platform_tag. The tags are as defined in PEP 0425.

Python tags look like cp27 cp34 cp35 cp36

Platform tags look like macosx_10_6_intel manylinux1_x86_64 manylinux1_i386 win32 win_amd64

You can also use shell-style globbing syntax (as per fnmatch)

Example: cp27-macosx_10_6_intel (don't build on Python 2 on Mac)
Example: cp27-win* (don't build on Python 2.7 on Windows)
Example: cp34-* cp35-* (don't build on Python 3.4 or Python 3.5)

--

Example YML syntax

example .travis.yml environment variables env: global: - CIBW_TEST_REQUIRES=nose - CIBW_TEST_COMMAND="nosetests {project}/tests"

example appveyor.yml environment variables environment: global: CIBW_TEST_REQUIRES: nose CIBW_TEST_COMMAND: "nosetests {project}\\tests"

Delivering to PyPI

After you've built your wheels, you'll probably want to deliver them to PyPI.

Manual method

On your development machine, do the following...

# Clear out your 'dist' folder. 
rm -rf dist
# Make a source distribution
python setup.py sdist

# 🏃🏻
# Go and download your wheel files from wherever you put them. Put 
# them all into the 'dist' folder.

# Upload using 'twine' (you may need to 'pip install twine')
twine upload dist/*

Semi-automatic method using wheelhouse-uploader

Obviously, manual steps are for chumps, so we can automate this a little by using wheelhouse-uploader.

Quick note from me - using S3 as a storage didn't work due to a bug in libcloud. Feel free to use my fork of that package that fixes the bug pip install https://github.com/joerick/libcloud/archive/v1.5.0-s3fix.zip

Automatic method

If you don't need much control over the release of a package, you can set up cibuildwheel to deliver the wheels straight to PyPI. This doesn't require any cloud storage to work - you just need to bump the version and tag it.

Check out this example repo for instructions on how to set this up.

It didn't work!

If your wheel didn't compile, check the list below for some debugging tips.

• A mistake in your config. To quickly test your config without doing a git push and waiting for your code to build on CI, you can run the Linux build in a Docker container. On Mac or Linux, with Docker running, try cibuildwheel --platform linux. You'll have to bring your config into the current environment first.
• Missing dependency. You might need to install something on the build machine. You can do this in .travis.yml or appveyor.yml, with apt-get, brew or whatever Windows uses :P . Given how the Linux build works, we'll probably have to build something into cibuildwheel. Let's chat about that over in the issues!
• Windows: missing C feature. The Windows C compiler doesn't support C language features invented after 1990, so you'll have to backport your C code to C90. For me, this mostly involved putting my variable declarations at the top of the function like an animal.

Working examples

Here are some repos that use cibuildwheel.

• pyinstrument_cext

Add repo here! Send a PR.

Legal note

Since cibuildwheel runs the wheel through delocate or auditwheel, it will automatically bundle library dependencies. This is similar to static linking, so it might have some licence implications. Check the license for any code you're pulling in to make sure that's allowed.

Changelog

0.4.0

• Fixed a bug that was increasing the build time by building the wheel twice. This was a problem for large projects that have a long build time. If you're upgrading and you need the old behaviour, use CIBW_BEFORE_BUILD={pip} install ., or install exactly the dependencies you need in CIBW_BEFORE_BUILD. See #18.

0.3.0

• Removed Python 2.6 support on Linux (#12)

0.2.1

11 June 2017

• Changed the build process to install the package before building the wheel - this allows direct dependencies to be installed first (#9, thanks @tgarc!)
• Added Python 3 support for the main process, for systems where Python 3 is the default (#8, thanks @tgarc).

0.2.0

13 April 2017

• Added CIBW_SKIP option, letting users explicitly skip a build
• Added CIBW_BEFORE_BUILD option, letting users run a shell command before the build starts

0.1.3

31 March 2017

• First public release!

Contributing

Wheel-building is pretty complex. I expect users to find many edge-cases - please help the rest of the community out by documenting these, adding features to support them, and reporting bugs.

I plan to be pretty liberal in accepting pull requests, as long as they align with the design goals below.

cibuildwheel is indie open source. I'm not paid to work on this.

Design Goals

• cibuildwheel should wrap the complexity of wheel building.
• The user interface to cibuildwheel is the build script (e.g. .travis.yml). Feature additions should not increase the complexity of this script.
• Options should be environment variables (these lend themselves better to YML config files). They should be prefixed with CIBW_.
• Options should be generalise to all platforms. If platform-specific options are required, they should be namespaced e.g. CIBW_TEST_COMMAND_MACOS

Other notes:

• The platforms are very similar, until they're not. I'd rather have straight-forward code than totally DRY code, so let's keep airy platfrom abstractions to a minimum.
• I might want to break the options into a shared config file one day, so that config is more easily shared. That has motivated some of the design decisions.

Maintainers

• Joe Rickerby @joerick
• Tomas Garcia @tgarc

Credits

cibuildwheel stands on the shoulders of giants. Massive props to-

• ⭐️ @matthew-brett for matthew-brett/multibuild and matthew-brett/delocate
• @PyPA for the manylinux Docker images pypa/manylinux
• @ogrisel for wheelhouse-uploader and run_with_env.cmd
• @zfrenchee for help debugging many issues

See also

If cibuildwheel is too limited for your needs, consider matthew-brett/multibuild. multibuild is a toolbox for building a wheel on various platforms. It can do a lot more than this project - it's used to build SciPy!