Skip to content

Tracking issue for manylinux2010 rollout #179

Closed

Description

@ncoghlan

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 pip 19.0 to install manylinux2010 wheels (PR: Manylinux2010 pip#5410)
  • Update pip 9.x to install manylinux2010 wheels (needed to avoid the manylinux2010 rollout being delayed by the Python API break between pip 9.x and pip 10.x) (@ncoghlan: skip for now, wait and see if we get complaints about needing this)
  • Update pipenv to install manylinux2010 wheels (needed due to pipenv vendoring pip, so the support depends on the version of pipenv being used, rather than the version of pip in the host or target environments)

Enable publication of manylinux2010 wheel archives:

Management of transition from manylinux1:

Additional projects to consider once core capability support has rolled out:

Tagging @takluyver @markrwilliams as the PEP 571 authors, and @di and @brainwane from the PyPI/PSF side of things.

Activity

  1. markrwilliams commented on Apr 14, 2018

    @markrwilliams
  2. takluyver commented on Apr 15, 2018

    @takluyver
    Member

    Updating the spec page on PyPUG:

    pypa/packaging.python.org#470

  3. added a commit that references this issue on May 12, 2018
  4. mayeut commented on May 12, 2018

    @mayeut
    Member

    Confirm that twine will upload manylinux2010 wheel archives

    Confirmed

    Update warehouse to accept manylinux2010 wheel uploads

    PR: pypi/warehouse#3951

  5. added a commit that references this issue on May 14, 2018
  6. di commented on May 14, 2018

    @di
    SponsorMember

    pypi/warehouse#3951 has been merged.

  7. wtolson commented on May 15, 2018

    @wtolson

    pip merge request has been updated here: pypa/pip#5410

  8. wtolson commented on May 15, 2018

    @wtolson

    auditwheel merge request has been updated here: pypa/auditwheel#92

  9. armudgal commented on May 17, 2018

    @armudgal
    Contributor

    Hi,
    First of all great job with this, I just wanted to know is there an estimate when the manylinux2010 will roll-out. Thanks :)

  10. takluyver commented on May 17, 2018

    @takluyver
    Member

    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.

  11. armudgal commented on May 20, 2018

    @armudgal
    Contributor

    Oh, thanks for the information

  12. techalchemy commented on May 23, 2018

    @techalchemy
    Member

    @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

  13. westurner commented on Sep 17, 2018

    @westurner
  14. safijari commented on Oct 13, 2018

    @safijari

    Other than the open pull requests needing to get merged, is there any more left to do for this effort? How can I help?

  15. ehashman commented on Nov 18, 2018

    @ehashman
    Member

    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.

  16. 123 remaining items

  17. JonasVautherin commented on Oct 14, 2019

    @JonasVautherin

    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?

  18. mayeut commented on Oct 14, 2019

    @mayeut
    Member

    @JonasVautherin,

    Intuitively, it sounds like if my project builds with manylinux1, then it is "more compatible" than if it only built with manylinux2010.

    That's true, however

    So anyway I still want to keep manylinux1 to support as many linux flavours as possible. Is that wrong?

    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)

  19. mayeut commented on Oct 14, 2019

    @mayeut
    Member

    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):

  20. snowman2 commented on Nov 7, 2019

    @snowman2

    Needing pip>=19.0.0 is causing some troubles in pyproj in this issue pyproj4/pyproj#477. Thoughts?

  21. di commented on Nov 7, 2019

    @di
    SponsorMember

    @snowman2 Unfortunately we can't go back in time and add manylinux2010 support to earlier pip versions. Can the project target manylinux1 instead? It's not clear to me from that issue what the problem is.

  22. snowman2 commented on Nov 7, 2019

    @snowman2

    Thanks for the information!

    It's not clear to me from that issue what the problem is.

    Mostly just relaying the issues so y'all are aware.

    Can the project target manylinux1

    Are there issues doing both?

  23. veblush commented on Nov 7, 2019

    @veblush
    Contributor

    Since gRPC Python started distributing both manylinux1 and manylinux2010, it might be useful to see download stats for gRPC 1.25 as of today:

    • manylinux2010: 83%
    • manylinux1: 17%

    Definitely, manylinux2010 is a primary platform now for gRPC users. For manylinux1 case, it's not because their environment are not compliant with manylinux2010 but because their pip is older than 19.

  24. veblush commented on Jan 29, 2020

    @veblush
    Contributor

    Please update the bullet point for "Distinguish manylinux2010 and manylinux1 images in dockercross" since they have manylinux1, manylinux2010, and manylinux2014 now.

  25. di commented on Jan 29, 2020

    @di
    SponsorMember

    Please update the bullet point for "Distinguish manylinux2010 and manylinux1 images in dockercross" since they have manylinux1, manylinux2010, and manylinux2014 now.

    Thanks! Done.

  26. ehashman commented on Feb 8, 2020

    @ehashman
    Member

    Will this issue ever die? Surely we can call the manylinux2010 rollout complete, now.

  27. di commented on Feb 8, 2020

    @di
    SponsorMember

    I agree!

  28. jbarlow83 commented on Feb 8, 2020

    @jbarlow83
  29. brainwane commented on Feb 9, 2020

    @brainwane

    Thanks all!

    Discussed some further documentation/message-spreading opportunities on Discourse.

  30. added a commit that references this issue on Apr 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions