Older archives: https://groups.google.com/forum/#!forum/manylinux-discuss
The goal of the manylinux project is to provide a convenient way to
distribute binary Python extensions as wheels on Linux. This effort
has produced PEP 513 which
is further enhanced by PEP 571
manylinux2010_i686 platform tags.
PEP 513 defined
manylinux1_i686 platform tags
and the wheels were built on Centos5. Centos5 reached End of Life (EOL) on
March 31st, 2017 and thus PEP 571 was proposed.
Code and details regarding
manylinux1 can be found here:
||Client-side pip version required|
||pip >= 19.3|
||pip >= 19.0|
||pip >= 8.1.0|
The manylinux2010 tags allow projects to distribute wheels that are automatically installed (and work!) on the vast majority of desktop and server Linux distributions.
This repository hosts several manylinux-related things:
Building manylinux-compatible wheels is not trivial; as a general rule, binaries built on one Linux distro will only work on other Linux distros that are the same age or newer. Therefore, if we want to make binaries that run on most Linux distros, we have to use a very old distro -- CentOS 6.
Rather than forcing you to install CentOS 6 yourself, install Python, etc., we provide Docker images where we've done the work for you. The images are uploaded to quay.io and are tagged for repeatable builds.
These images are rebuilt using Travis-CI on every commit to this repository; see the docker/ directory for source code.
The images currently contain:
- CPython 2.7, 3.5, 3.6, 3.7 & 3.8, installed in
/opt/python/<python tag>-<abi tag>. The directories are named after the PEP 425 tags for each environment -- e.g.
/opt/python/cp27-cp27mucontains a wide-unicode CPython 2.7 build, and can be used to produce wheels named like
- Devel packages for all the libraries that PEP 571 allows you to assume are present on the host system
- The auditwheel tool
Note that prior to CPython 3.3, there were two ABI-incompatible ways
of building CPython:
--enable-unicode=ucs4. We provide both versions
/opt/python/cp27-cp27m for narrow-unicode,
/opt/python/cp27-cp27mu for wide-unicode). NB: essentially all
Linux distributions configure CPython in
--enable-unicode=ucs4) mode, but
are also encountered in the wild. Other less common or virtually
unheard of flag combinations (such as
--without-pymalloc (absence of
m)) are not provided.
Note that starting with CPython 3.8,
sys.abiflags became an empty string: the
m flag for pymalloc
became useless (builds with and without pymalloc are ABI compatible) and so has
been removed. (e.g.
Building Docker images
To build the Docker images, you will need to fetch the tarballs to
docker/sources/ prior to building. This can be done with the
provided prefetch script, after which you can proceed with building.
Please run the following command from the current (root) directory:
$ PLATFORM=$(uname -m) TRAVIS_COMMIT=latest ./build.sh
An example project which builds 64-bit wheels for each Python interpreter
version can be found here: https://github.com/pypa/python-manylinux-demo. The
repository also contains demo to build 32-bit and 64-bit wheels with
This demonstrates how to use these docker images in conjunction with auditwheel to build manylinux-compatible wheels using the free travis ci continuous integration service.
(NB: for the 32-bit images running on a 64-bit host machine, it's necessary to run everything under the command line program linux32, which changes reported architecture in new program environment. See this example invocation)
The PEP itself
The official version of PEP 513 is stored in the PEP repository, but we also have our own copy here. This is where the PEP was originally written, so if for some reason you really want to see the full history of edits it went through, then this is the place to look.
The proposal to upgrade
manylinux2010 after Centos5
reached EOL was discussed in PEP 571.
This repo also has some analysis code that was used when putting
together the original proposal in the
If you want to read the full discussion that led to the original policy, then lots of that is here: https://groups.google.com/forum/#!forum/manylinux-discuss
The distutils-sig archives for January 2016 also contain several threads.
Code of Conduct
Everyone interacting in the manylinux project's codebases, issue trackers, chat rooms, and mailing lists is expected to follow the PSF Code of Conduct.