Repository navigation
Closed
Description
I've accepted the manylinux2010 PEP, so that's now an active interoperability standard: https://www.python.org/dev/peps/pep-0571/
However, there are a number of further steps needed before folks can actually make use of that new baseline, and the order of operations matters (since building manylinux2010 wheels isn't very useful if installers won't install them):
Essential client support:
- Update
pip19.0 to installmanylinux2010wheels (PR: Manylinux2010 pip#5410) -
Update(@ncoghlan: skip for now, wait and see if we get complaints about needing this)pip9.x to installmanylinux2010wheels (needed to avoid themanylinux2010rollout being delayed by the Python API break betweenpip9.x andpip10.x) - Update
pipenvto installmanylinux2010wheels (needed due topipenvvendoringpip, so the support depends on the version of pipenv being used, rather than the version ofpipin the host or target environments)
Enable publication of manylinux2010 wheel archives:
- Update
auditwheelto emitmanylinux2010wheel archives (PR: Manylinux2010 auditwheel#92) - Confirm that
twinewill uploadmanylinux2010wheel archives - Update
warehouseto acceptmanylinux2010wheel uploads (Allow manylinux2010 wheel upload pypi/warehouse#3951) - Provide a
manylinux2010build environment: https://quay.io/repository/pypa/manylinux2010_x86_64
Management of transition from manylinux1:
- Update https://packaging.python.org/specifications/platform-compatibility-tags/ to cover
manylinux2010, with the caveat that it doesn't actually have broad tooling support yet - Reword the "not yet widely supported" caveat from the platform compatibility tagging page to instead specify the minimum required versions of
auditwheelto emit manylinux2010 packages, andpipandpipenvto install them (Update manylinux tags section packaging.python.org#656) - Nominate a timeline and/or "percentage of PyPI downloads by
manylinux2010compatible installers" for switching the default build environment andauditwheeloutput tomanylinux2010
Additional projects to consider once core capability support has rolled out:
- Option to target
manylinux2010instead ofmanylinux1in https://github.com/joerick/cibuildwheel#readme - Option to target
manylinux2010instead ofmanylinux1in https://github.com/matthew-brett/multibuild#readme - Distinguish
manylinux2010andmanylinux1images in https://github.com/dockcross/dockcross#readme - ... any other suggestions?
Tagging @takluyver @markrwilliams as the PEP 571 authors, and @di and @brainwane from the PyPI/PSF side of things.
Reacted by Dustin Ingram, Axel Huebl, jbarlow, Venelin Stoykov, Kenichi Maehashi, Roman Yurchak, Arushit, Alexander Clausen, Dilawar Singh, Matt McCormick and 7 more
Metadata
Metadata
Assignees
Labels
No labels
Activity
markrwilliams commentedon Apr 14, 2018
See:
pypa/auditwheel#88
pypa/pip#5008
takluyver commentedon Apr 15, 2018
Updating the spec page on PyPUG:
pypa/packaging.python.org#470
Allow manylinux2010 wheel upload
mayeut commentedon May 12, 2018
Confirmed
PR: pypi/warehouse#3951
Allow manylinux2010 wheel upload (#3951)
di commentedon May 14, 2018
pypi/warehouse#3951 has been merged.
wtolson commentedon May 15, 2018
pip merge request has been updated here: pypa/pip#5410
wtolson commentedon May 15, 2018
auditwheel merge request has been updated here: pypa/auditwheel#92
armudgal commentedon May 17, 2018
Hi,
First of all great job with this, I just wanted to know is there an estimate when the
manylinux2010will roll-out. Thanks :)takluyver commentedon May 17, 2018
There's no one roll-out date, because support needs to be added to various different tools in the ecosystem (see the list at the top of the issue). I imagine that it's probably a matter of a few weeks to a few months before you can use it and expect it to work.
armudgal commentedon May 20, 2018
Oh, thanks for the information
techalchemy commentedon May 23, 2018
@ncoghlan Pipenv will have pip 10 support after we merge pypa/pipenv#2255 which un-vendors pip9 completely, and bundles a patched version of pip10 which can be re-vendored and patched when updates land (this was possible because pip-tools accepted my PR which makes them pip10 compatible as well)
so whenever the pr lands in pip we can make the call about whether to actually go ahead and pull that into our patched version before it's released (technically we could do this now, even) and we will be set
westurner commentedon Sep 17, 2018
"SEC: Spectre variant 2: GCC:
-mindirect-branch=thunk -mindirect-branch-register"https://mail.python.org/mm3/archives/list/[email protected]/thread/4BGE226DB5EWIAT5VCJ75QD5ASOVJZCM/
safijari commentedon Oct 13, 2018
Other than the open pull requests needing to get merged, is there any more left to do for this effort? How can I help?
ehashman commentedon Nov 18, 2018
I have merged support for manylinux2010 in auditwheel. Will be cutting a release candidate today.
Note that auditwheel will default to assigning the strictest possible tag, hence it is possible for a binary built inside the manylinux2010 image to receive a manylinux1 tag given that the wheel's symbols match the stricter manylinux1 policy.
123 remaining items
JonasVautherin commentedon Oct 14, 2019
One thing that is not clear to me is whether I should move to manylinux2010 or not. Intuitively, it sounds like if my project builds with manylinux1, then it is "more compatible" than if it only built with manylinux2010. So anyway I still want to keep manylinux1 to support as many linux flavours as possible. Is that wrong?
mayeut commentedon Oct 14, 2019
@JonasVautherin,
That's true, however
It's probably wrong. I'd say most of linux flavors that came out before 2010 are now EOL meaning they do not receive any security updates. Time to move on. (manylinux2010 base OS, which is centos6 will reach end of life in November of 2020)
mayeut commentedon Oct 14, 2019
A partial overview of manylinux2010 adoption through quay.io stats (yes, it's partial but can give an estimate which might not be too biased):
snowman2 commentedon Nov 7, 2019
Needing
pip>=19.0.0is causing some troubles inpyprojin this issue pyproj4/pyproj#477. Thoughts?di commentedon Nov 7, 2019
@snowman2 Unfortunately we can't go back in time and add
manylinux2010support to earlierpipversions. Can the project targetmanylinux1instead? It's not clear to me from that issue what the problem is.snowman2 commentedon Nov 7, 2019
Thanks for the information!
Mostly just relaying the issues so y'all are aware.
Are there issues doing both?
veblush commentedon Nov 7, 2019
Since gRPC Python started distributing both
manylinux1andmanylinux2010, it might be useful to see download stats for gRPC 1.25 as of today:manylinux2010: 83%manylinux1: 17%Definitely,
manylinux2010is a primary platform now for gRPC users. Formanylinux1case, it's not because their environment are not compliant withmanylinux2010but because their pip is older than 19.veblush commentedon Jan 29, 2020
Please update the bullet point for "Distinguish manylinux2010 and manylinux1 images in dockercross" since they have manylinux1, manylinux2010, and manylinux2014 now.
di commentedon Jan 29, 2020
Thanks! Done.
ehashman commentedon Feb 8, 2020
Will this issue ever die? Surely we can call the manylinux2010 rollout complete, now.
di commentedon Feb 8, 2020
I agree!
jbarlow83 commentedon Feb 8, 2020
brainwane commentedon Feb 9, 2020
Thanks all!
Discussed some further documentation/message-spreading opportunities on Discourse.
PEP 571: Change status to Final