[
https://issues.apache.org/jira/browse/ARROW-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873163#comment-15873163
]
Wes McKinney commented on ARROW-566:
------------------------------------
Well, the shared libraries need to end up effectively in {{$LD_LIBRARY_PATH}}
or loaded dynamically -- conda works as a tool for building a LD_LIBRARY_PATH
for the libarrow shared libraries. One option you can use is to load the
`libpyarrow.so` using ctypes based on the absolute module path of `pyarrow`
(this is similar to how NumPy's C-level interoperability works). I presume
you're statically-linking the dependencies in pyarrow?
> Python: Deterministic position of libarrow in manylinux1 wheels
> ---------------------------------------------------------------
>
> Key: ARROW-566
> URL: https://issues.apache.org/jira/browse/ARROW-566
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python
> Reporter: Uwe L. Korn
> Assignee: Uwe L. Korn
>
> To link other Python wheels to the {{pyarrow}}, the position and name of all
> shared libraries should be deterministic. Currently using {{libarrow}} in
> other Python packages is only possible using the conda packaging stack, via
> pip installable paths.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
