Mailing-List: contact dev-help@arrow.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@arrow.apache.org
Date: Tue, 6 Dec 2016 06:05:59 +0000 (UTC)
From: "Uwe L. Korn (JIRA)" <jira@apache.org>
To: dev@arrow.apache.org
Message-ID: <JIRA.13013380.1476846588000.446584.1481004359636@Atlassian.JIRA>
In-Reply-To: <JIRA.13013380.1476846588000@Atlassian.JIRA>
References: <JIRA.13013380.1476846588000@Atlassian.JIRA> <JIRA.13013380.1476846588996@arcas>
Subject: [jira] [Commented] (ARROW-341) [Python] Making libpyarrow available
 to third parties
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 06 Dec 2016 06:06:01 -0000


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

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

Another functionality that could be shared to other (non Cython) third-party libraries is the conversion code of C++ to Python objects (i.e. {{arrow::Table}} -> {{pyarrow.Table}}).

At first glance this looked like something easy but it will possibly require that we move the definition of the Python structs ({{pyarrow.Table}}) to the C++ code from Cython. This would make a it a bit more hard to maintain.

> [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)