sjperkins commented on PR #33805: URL: https://github.com/apache/arrow/pull/33805#issuecomment-1400224374
> Is there a benefit for our users to _publish_ such wheels in addition to manylinux2014? > > (note "publish", so push to PyPI, regardless of that it can be useful to ensure we can already built such wheels) Two interlinked reason: 1. Quoting from https://pypackaging-native.github.io/key-issues/native-dependencies/cpp_deps/ > C++ ABI has been an issue for quite a while. Most C++ developers and projects want to use the new ABI, however due to the old manylinux standard and depending on devtoolset forces the use of the old C++ ABI (_GLIBCXX_USE_CXX11_ABI=0). Projects using modern C++14/17 typically want to use the new ABI. This is still quite difficult. It's now possible with manylinux_2_28, but requires building duplicate sets of wheels[1](https://pypackaging-native.github.io/key-issues/native-dependencies/cpp_deps/#fn:1) (also manylinux2014 for compatibility with older distros like Ubuntu 18.04 and CentOS 8, that will still use the old ABI). 2. It'd be useful for building extensions that want the newer ABI against manylinux_2_28. https://arrow.apache.org/docs/python/integration/extending.html#building-extensions-against-pypi-wheels -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
