On Fri, Nov 27, 2020 at 10:42 AM Kirill Lykov wrote:
>
> ARROW_COMPUTE was enabled because ARROW_PYTHON was enabled (I double
> checked).
> And sanity check helped -- I should be in python folder, not in the root
> folder of arrow repo, thanks!
>
> I wonder if there a way to detect if compute
In my experience, if we turn on DARROW_PYTHON and DARROW_COMPUTE to ON and
do build from source and then just build the wheel from the source would
install the libarrow_python.so and within the site-packages for Pyarrow
you can also get the compute*.so as well. If you used a virtual environment
ARROW_COMPUTE was enabled because ARROW_PYTHON was enabled (I double
checked).
And sanity check helped -- I should be in python folder, not in the root
folder of arrow repo, thanks!
I wonder if there a way to detect if compute module is present by looking
into *.so files.
Because at our internal
Arrow Build Report for Job nightly-2020-11-27-0
All tasks:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-11-27-0
Failed Tasks:
- example-cpp-minimal-build-static-system-dependency:
URL:
Le 27/11/2020 à 06:07, Micah Kornfield a écrit :
> Could we hold off for at least a few days, I'd like to run this by some
> colleagues.
Certainly.
> Are there any options for maintaining a functioning CI for
> Python 3.5?
I don't know. Interested people would have to investigate :-)
