jorisvandenbossche commented on issue #38338: URL: https://github.com/apache/arrow/issues/38338#issuecomment-1770463755
> I think what happened here is that switching to 3.12, I was no longer on the golden path of having a wheel (built by the CI/CD) with the extensions enabled. So, `pip` fell back to calling out to `setuptools` to build from the source dist, and by default, that's with all of the extension flags set to "off". Yes, that sounds as a correct summary. > One question I have is generally why all of the Cython extensions appear to be disabled in the package `setup.py`. Am I correct in understanding this is just a default state and that these normally be then enabled (using the environment variables) in CI/CD tasks when wheels are built and published? Yes, essentially our build setup is by default a relative minimal build, with the assumption you have to enable the additional feature you want (the same is true when building Arrow C++ from source). Although in the case of pyarrow, when it's building against an Arrow C++ build that already made such choices, it might be nice to automatically infer whatever is supported by libarrow (if you build both from source that is certainly possible, not sure if that would also work when building agasint a brew-installed Arrow C++) -- 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]
