It seems like a good idea to attempt to make this change. The most
difficult thing might be projects that use the arrow/python/pyarrow.h
C++ API, so we would have to provide a viable migration path for
those. turbodbc is one example
https://github.com/blue-yonder/turbodbc/search?l=C%2B%2B&q=pyarro
I agree with this proposal, the Arrow C++ library does not need to depend
on Python or PyArrow code.
AFAIU this will eliminate the use of -DARROW_PYTHON build flag for Arrow
C++ given that Python-related code will be compiled with PyArrow builds.
Besides the use of "ARROW_PYTHON" env variable in CM
I definitely think this is desirable.
There's probably going to be a bit of work getting it to pass on all CI
(including the various nightly builds).
Regards
Antoine.
Le 16/08/2021 à 17:08, Alessandro Molina a écrit :
PyArrow is currently full Cython codebase, but in reality it relies on
This seems reasonable as long as it is actually feasible (the dependencies
are cleanly separable)..
A while ago I had a proof of concept bazel build working that was able to
automatically build the changes together.
On Monday, August 16, 2021, David Li wrote:
> I support this. In the past I had
I support this. In the past I had to effectively do this manually to build
Arrow/PyArrow in a monorepo (to build for multiple Python versions
simultaneously without having conflicting copies of Arrow for each Python
version). From what I remember, there's some usage of Arrow-internal headers
th
PyArrow is currently full Cython codebase, but in reality it relies on some
classes and functions that are implemented in C++ within the src/python
directory ( https://github.com/apache/arrow/tree/master/cpp/src/arrow/python
). Especially for numpy/pandas conversion code that has to interface with
