[
https://issues.apache.org/jira/browse/ARROW-16340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637098#comment-17637098
]
Kouhei Sutou commented on ARROW-16340:
--------------------------------------
I don't recommend the approach because the approach mixes 2 Apache Arrow C++
libraries.
bq. 1) Do you think if it helps if I keep pyarrow's version and Arrow C++
library version always consistent (for example, both using 10.0.0)?
It's better but I don't recommend mixing Apache Arrow C++ library in pyarrow's
wheel and Apache Arrow C++ library from vcpkg.
bq. 2) If I use the official pyarrow (in Python) wheel and (pyarrow C++ library
+ Arrow C++ library, both compiled from vcpkg),
I don't recommend mixing them.
bq. is it any better than using the C data stream API?
You can use simpler API. But it's not the biggest problem. You can use either
API you like if you don't mix Apache Arrow C++ libraries.
bq. You said `you mix multiple Apache Arrow C++ libraries` and this could cause
unexpected behavior, but it seems even if I don't use this approach, as long as
I use pyarrow wheel in Python, I may run into such some unexpected problem, is
it correct?
Sorry. I couldn't understand this. Does it mean that you use only pyarrow
wheel? (You don't mix 2 Apache Arrow C++ libraries?)
> [C++][Python] Move all Python related code into PyArrow
> -------------------------------------------------------
>
> Key: ARROW-16340
> URL: https://issues.apache.org/jira/browse/ARROW-16340
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Python
> Reporter: Alenka Frim
> Assignee: Alenka Frim
> Priority: Major
> Labels: pull-request-available
> Fix For: 10.0.0
>
> Time Spent: 33h 10m
> Remaining Estimate: 0h
>
> Move {{src/arrow/python}} directory into {{pyarrow}} and arrange PyArrow to
> build it.
> More details can be found on this thread:
> https://lists.apache.org/thread/jbxyldhqff4p9z53whhs95y4jcomdgd2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
