Hi, I don't think we followed this up. I've created a JIRA ticket to track it: https://issues.apache.org/jira/browse/ARROW-16747
Thanks, Raúl On Mon, May 9, 2022 at 2:53 PM Joris Van den Bossche < jorisvandenboss...@gmail.com> wrote: > +1 as well > > Joris > > On Thu, 5 May 2022 at 22:29, Sutou Kouhei <k...@clear-code.com> wrote: > > > +1 > > > > Our next major release will be in July or August. I think > > that pypa will drop support for manylinux2010 officially > > when release a next major version. > > > > Thanks, > > -- > > kou > > > > In <CANva0dhxrkeGoUPFVuB8=319-iottot-_qoyivd1abyjv2o...@mail.gmail.com> > > "[DISC] (Python) Dropping support for manylinux2010" on Thu, 5 May 2022 > > 13:01:47 +0200, > > Jacob Wujciak <ja...@voltrondata.com> wrote: > > > > > Hi all, > > > > > > I would like to propose that we drop support for manylinux2010. > > > > > > 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]. > > > > > > [1]: > > > > > > https://access.redhat.com/support/policy/updates/errata/#Life_Cycle_Dates > > > [2]: https://github.com/pypa/manylinux/issues/1281 > > > [3]: https://mayeut.github.io/manylinux-timeline/ > > > [4]: https://pypistats.org/packages/pyarrow > > > [5]: https://pip.pypa.io/en/stable/news/#v19-3 > > > [6]: https://issues.apache.org/jira/browse/ARROW-16476 > > > > > > Thanks, > > > Jacob > > >
