jorisvandenbossche commented on issue #39532: URL: https://github.com/apache/arrow/issues/39532#issuecomment-1883045140
Some other observations / relevant bits from the linked issues: * Since numpy 1.25, we don't need `oldest-supported-numpy` anymore (https://numpy.org/devdocs/release/1.25.0-notes.html#compiling-against-the-numpy-c-api-is-now-backwards-compatible-by-default and https://github.com/scipy/oldest-supported-numpy#deprecation-notice-for-numpy-20), so for newer Python versions (where the minimum supported version of numpy is <=1.25), we can start compiling with the latest numpy * At the moment, pip install pyarrow in an environment with numpy 2.0, the import of pyarrow fails. So at a minimum, we should add a `numpy<2.0` pin in the release branch * If we want wheels that support both numpy 1.x and 2.0 at runtime, we need to build our wheels with numpy 2.0 (https://numpy.org/devdocs/dev/depending_on_numpy.html#numpy-2-0-specific-advice). The recommendation is to start doing that (and then a numpy<2.0 pin in the released version is no longer needed) once numpy 2.0rc1 is out. This is targeted for around 1 Feb 2024, but other projects already started building their wheels with numpy 2.0.dev, as far as I understand (eg https://github.com/scikit-learn/scikit-learn/pull/27735, or that is only for the nightly 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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
