You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@arrow.apache.org by "Uwe L. Korn (JIRA)" <ji...@apache.org> on 2016/10/19 06:29:58 UTC

[jira] [Commented] (ARROW-341) [Python] Making libpyarrow available to third parties

    [ https://issues.apache.org/jira/browse/ARROW-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587833#comment-15587833 ] 

Uwe L. Korn commented on ARROW-341:
-----------------------------------

Sounds ok to me.

Then we may still have a {{libpyarrrow.so}} but that will solely have code that is shared between the {{pyarrow}} modules and not to be exposed externally?

> [Python] Making libpyarrow available to third parties
> -----------------------------------------------------
>
>                 Key: ARROW-341
>                 URL: https://issues.apache.org/jira/browse/ARROW-341
>             Project: Apache Arrow
>          Issue Type: New Feature
>          Components: Python
>            Reporter: Wes McKinney
>
> We may want to link against this library in pandas 2.0 -- [~xhochy] what do you think? One option is that we could move the Python glue into the C++ library and create a leaf lib {{libarrow_python.so}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)