jorisvandenbossche commented on PR #43325: URL: https://github.com/apache/arrow/pull/43325#issuecomment-2248451171
This is also assuming here that we are fine with actually removing the `PYARROW_INSTALL_TESTS=0` option. I don't think many people are using this (I verified that conda-forge is not using it, they have there own handling of providing a separate `pyarrow-tests` output). I found only a few occurrences through a github code search (https://github.com/altlinux/specs/blob/f271ff0e6e3abfd44ce06c1b88655570b58060ec/a/arrow/arrow.spec#L532 https://github.com/ehenry2/minimal-pyarrow/blob/a81244cce71b84d131a547cc618ba065eb1b658f/build.sh#L55 https://github.com/mamckee/azurelinux/blob/253b6a9ff1f1708c2a55f7fde8292340374f425f/SPECS/libarrow/libarrow.spec#L351). I assume that in principle we could still have some logic in setup.py to override the included files from pyproject.toml, but that's probably not worth it? -- 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]
