simlock
병렬 코딩 에이전트가 동일 시뮬레이터를 놓고 충돌하지 않도록 제어 평면 제공
최소 설정으로 모든 플랫폼용 파이썬 휠을 빌드합니다
🎡 Build Python wheels for all the platforms with minimal configuration.
개발 도구Python · ShellGitHub @pypa직접 설치운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗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 GitHub Actions, Azure Pipelines, CircleCI, and GitLab CI - and it builds and tests your wheels across all of your platforms.
While cibuildwheel itself requires a recent Python version to run (we support the last three releases), it can target the following versions to build wheels:
| macOS Intel | macOS Apple Silicon | Windows 64bit | Windows 32bit | Windows Arm64 | manylinuxmusllinux x86_64 | manylinuxmusllinux i686 | manylinuxmusllinux aarch64 | manylinuxmusllinux ppc64le | manylinuxmusllinux s390x | manylinuxmusllinux armv7l | Android | iOS | Pyodide | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CPython 3.9 | ✅ | ✅ | ✅ | ✅ | ✅2 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅4 | N/A | N/A | N/A |
| CPython 3.10 | ✅ | ✅ | ✅ | ✅ | ✅2 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅4 | N/A | N/A | N/A |
| CPython 3.11 | ✅ | ✅ | ✅ | ✅ | ✅2 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅4 | N/A | N/A | N/A |
| CPython 3.12 | ✅ | ✅ | ✅ | ✅ | ✅2 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅4 | N/A | N/A | ✅3 |
| CPython 3.13 | ✅ | ✅ | ✅ | ✅ | ✅2 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅4 | ✅ | ✅ | ✅ |
| CPython 3.14 | ✅ | ✅ | ✅ | ✅ | ✅2 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅4 | ✅ | ✅ | ✅ |
| CPython 3.15 | ✅ | ✅ | ✅ | ✅ | ✅2 | ✅ | ✅ | ✅ | ✅ | ✅ | ✅4 | ✅ | ✅ | ✅ |
| PyPy 3.9 v7.3 | ✅ | ✅ | ✅ | N/A | N/A | ✅1 | ✅1 | ✅1 | N/A | N/A | N/A | N/A | N/A | N/A |
| PyPy 3.10 v7.3 | ✅ | ✅ | ✅ | N/A | N/A | ✅1 | ✅1 | ✅1 | N/A | N/A | N/A | N/A | N/A | N/A |
1 PyPy & GraalPy are only supported for manylinux wheels.
2 Windows arm64 support is experimental.
3 Not supported on PyPI, uses old pyodide tag instead of pyemscripten. Requires pyodide-eol enable.
4 manylinux armv7l support is experimental. As there are no RHEL based image for this architecture, it's using an Ubuntu based image instead.
See the cibuildwheel 1 documentation if you need to build unsupported versions of Python, such as Python 2.
cibuildwheel runs inside a CI service. Supported platforms depend on which service you're using:
| Linux | macOS | Windows | Linux ARM | macOS ARM | Windows ARM | Android | iOS | Pyodide | |
|---|---|---|---|---|---|---|---|---|---|
| GitHub Actions | ✅ | ✅ | ✅ | ✅ | ✅ | ✅2 | ✅4 | ✅3 | ✅ |
| Azure Pipelines | ✅ | ✅ | ✅ | ✅ | ✅2 | ✅4 | ✅3 | ✅5 | |
| CircleCI | ✅ | ✅ | ✅ | ✅ | ✅45 | ✅35 | ✅5 | ||
| GitLab CI | ✅ | ✅ | ✅ | ✅1 | ✅ | ✅45 | ✅35 | ✅5 |
1 Requires emulation, distributed separately. Other services may also support Linux ARM through emulation or third-party build hosts, but these are not tested in our CI.
2 Uses cross-compilation. It is not possible to test arm64 on this CI platform.
3 Requires a macOS runner; runs tests on the simulator for the runner's architecture.
4 Building for Android requires the runner to be Linux x86_64, macOS ARM64 or macOS x86_64. Testing has additional requirements.
5 Builds may work, but are untested in cibuildwheel's CI.
To build manylinux, musllinux, macOS, and Windows wheels on GitHub Actions, you could use this .github/workflows/wheels.yml:
name: Build
on: [push, pull_request]
jobs:
build_wheels:
name: Build wheels on ${{ matrix.os }}
runs-on: ${{ matrix.os }}
strategy:
matrix:
os: [ubuntu-latest, ubuntu-24.04-arm, windows-latest, windows-11-arm, macos-15-intel, macos-latest]
steps:
- uses: actions/checkout@v6
with:
persist-credentials: false
# Used to host cibuildwheel
- uses: actions/setup-python@v6
- name: Install cibuildwheel
run: python -m pip install cibuildwheel==4.3.5
- name: Build wheels
run: python -m cibuildwheel --output-dir wheelhouse
# to supply options, put them in 'env', like:
# env:
# CIBW_SOME_OPTION: value
# ...
- uses: actions/upload-artifact@v6
with:
name: cibw-wheels-${{ matrix.os }}-${{ strategy.job-index }}
path: ./wheelhouse/*.whl
For more information, including PyPI deployment, and the use of other CI services or the dedicated GitHub Action, check out the documentation and the examples.
The following diagram summarises the steps that cibuildwheel takes on each platform.
Explore an interactive version of this diagram in the docs.
[!WARNING] Building and testing wheels executes arbitrary code from your project and its dependencies. Although cibuildwheel uses OCI containers and Pyodide for some builds, these provide no security guarantees - the code you're building and testing has full access to the environment that's invoking cibuildwheel.
If you cannot trust all the code that's pulled in, maintain good security hygiene: keep the job that builds distributions separate from the job that uploads them to PyPI, handle secrets and credentials with care and rotate them regularly, and follow the principle of least privilege when granting permissions. Do not store sensitive data on CI runners.
| Option | Description | |
|---|---|---|
| Build selection | platform | Override the auto-detected target platform |
buildskip | Choose the Python versions to build | |
archs | Change the architectures built on your machine by default. | |
project-requires-python | Manually set the Python compatibility of your project | |
enable | Enable building with extra categories of selectors present. | |
allow-empty | Suppress the error code if no wheels match the specified build identifiers | |
| Build customization | build-frontend | Set the tool to use to build, either "build" (default), "build[uv]", or "pip" |
config-settings | Specify config-settings for the build backend. | |
environment | Set environment variables | |
These options can be specified in a pyproject.toml file, or as environment variables, see configuration docs.
Here are some repos that use cibuildwheel.
| Name | CI | OS | Notes |
|---|---|---|---|
| scikit-learn | The machine learning library. A complex but clean config using many of cibuildwheel's features to build a large project with Cython and C++ extensions. | ||
| duckdb | DuckDB is a high-performance analytical database system | ||
| NumPy | The fundamental package for scientific computing with Python. | ||
| pytorch-fairseq | Facebook AI Research Sequence-to-Sequence Toolkit written in Python. | ||
| NCNN | ncnn is a high-performance neural network inference framework optimized for the mobile platform | ||
| Matplotlib | The venerable Matplotlib, a Python library with C++ portions | ||
| Tornado | Tornado is a Python web framework and asynchronous networking library. Uses stable ABI for a small C extension. | ||
| MyPy | The compiled version of MyPy using MyPyC. | ||
| Prophet |
ℹ️ That's just a handful, there are many more! Check out the Working Examples page in the docs.
Since cibuildwheel repairs the wheel with delocate, auditwheel, or delvewheel, it might automatically bundle dynamically linked libraries from the build machine.
It helps ensure that the library can run without any dependencies outside of the pip toolchain.
This is similar to static linking, so it might have some license implications. Check the license for any code you're pulling in to make sure that's allowed.
27 October 2026
22 October 2026
restoreKeys (#3022)21 October 2026
20 October 2026
10 October 2026
That's the last few versions.
ℹ️ Want more changelog? Head over to the changelog page in the docs.
For more info on how to contribute to cibuildwheel, see the docs.
Everyone interacting with the cibuildwheel project via codebase, issue tracker, chat rooms, or otherwise is expected to follow the PSF Code of Conduct.
Core:
Platform maintainers:
cibuildwheel stands on the shoulders of giants.
run_with_env.cmdMassive props also to-
Another very similar tool to consider is matthew-brett/multibuild. multibuild is a shell script toolbox for building a wheel on various platforms. It is used as a basis to build some of the big data science tools, like SciPy.
If you are building Rust wheels, you can get by without some of the tricks required to make GLIBC work via manylinux; this is especially relevant for cross-compiling, which is easy with Rust. See maturin-action for a tool that is optimized for building Rust wheels and cross-compiling.
| PyPy 3.11 v8.0 | ✅ | ✅ | ✅ | N/A | N/A | ✅1 | ✅1 | ✅1 | N/A | N/A | N/A | N/A | N/A | N/A |
| PyPy 3.12 v8.0 | ✅ | ✅ | ✅ | N/A | N/A | ✅1 | ✅1 | ✅1 | N/A | N/A | N/A | N/A | N/A | N/A |
| GraalPy 3.12 v25.0 | ✅ | ✅ | ✅ | N/A | N/A | ✅1 | N/A | ✅1 | N/A | N/A | N/A | N/A | N/A | N/A |
| GraalPy 3.13 v25.3 | N/A | ✅ | ✅ | N/A | N/A | ✅1 | N/A | ✅1 | N/A | N/A | N/A | N/A | N/A | N/A |
environment-pass| Set environment variables on the host to pass-through to the container. |
before-all | Execute a shell command on the build system before any wheels are built. |
before-build | Execute a shell command preparing each wheel's build |
xbuild-tools | Binaries on the path that should be included in an isolated cross-build environment. |
xbuild-files | Platform-specific files in the build environment |
repair-wheel-command | Execute a shell command to repair each built wheel |
manylinux-*-imagemusllinux-*-image | Specify manylinux / musllinux container images |
container-engine | Specify the container engine to use when building Linux wheels |
dependency-versions | Control the versions of the tools cibuildwheel uses |
pyodide-version | Specify the Pyodide version to use for pyodide platform builds |
| Auditing | audit-requires | Install Python dependencies for the audit step |
audit-command | Use a tool to check wheels before the end of the run |
| Testing | test-command | The command to test each built wheel |
before-test | Execute a shell command before testing each wheel |
test-sources | Paths that are copied into the working directory of the tests |
test-requires | Install Python dependencies before running the tests |
test-extras | Install your wheel for testing using extras_require |
test-groups | Specify test dependencies from your project's dependency-groups |
test-skip | Skip running tests on some builds |
test-environment | Set environment variables for the test environment |
test-runtime | Controls how the tests will be executed. |
| Debugging | build-verbosity | Increase/decrease the output of the build |
debug-keep-container | Keep the container after running for debugging. |
debug-traceback | Print full traceback when errors occur. |
log-fold-mode | Control CI log folding. |
| Tool for producing high quality forecasts for time series data that has multiple seasonality with linear or non-linear growth. |
| Triton | Self hosted runners |