You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket is to track it. The following was the main rationale to do it copied from the mail:
CentoOS 6, on which the manylinux2010 image is based, has been EOL for over
two years 1.
There is now also an official announcement by pypa that
manylinux2010 support will be dropped sometime in 2022 2 that has not
received any feedback on either Github or Discourse. Since the announcement
the percentage of affected users has dropped from ~7% to ~4% of Python 3.7
users 3. ~52% of pyarrow users are on 3.7 so only ~2% of pyarrow users 4 would potentially be affected by an issue fixed by updating pip 5.
We have already had several CI issues with the manylinux2010 builds that
required workarounds. There are now also issues with verification as there
are no aarch64 wheels for manylinux2010 6.
Antoine Pitrou / @pitrou:
The way I read the "Policy readiness for python 3.7" graph in https://mayeut.github.io/manylinux-timeline/ is that 92.7% of Python 3.7 users are manylinux2014-ready (on May 31st 2022), meaning that 7.3% are not. But you're right it's just a matter of installing pip, since basically 99.9% of the user base is glibc-compatible.
Joris Van den Bossche / @jorisvandenbossche:
Given the mailing list thread (and given how few users would be affect, maybe except for a pip update), I think it is fine to just go ahead here.
There seemed to be consensus on this mailing list thread to drop support for Manylinux 2010.
https://lists.apache.org/thread/dfsvcsmrmktgnqz9fyc9ym33zldwklyx
This ticket is to track it. The following was the main rationale to do it copied from the mail:
CentoOS 6, on which the manylinux2010 image is based, has been EOL for over
two years 1.
There is now also an official announcement by pypa that
manylinux2010 support will be dropped sometime in 2022 2 that has not
received any feedback on either Github or Discourse. Since the announcement
the percentage of affected users has dropped from ~7% to ~4% of Python 3.7
users 3. ~52% of pyarrow users are on 3.7 so only ~2% of pyarrow users
4 would potentially be affected by an issue fixed by updating pip 5.
We have already had several CI issues with the manylinux2010 builds that
required workarounds. There are now also issues with verification as there
are no aarch64 wheels for manylinux2010 6.
Reporter: Raúl Cumplido / @raulcd
Assignee: Raúl Cumplido / @raulcd
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-16747. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: