You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2018/01/24 02:40:00 UTC
[jira] [Resolved] (ARROW-1960) [Python] Pre-emptively import
TensorFlow if it is available
[ https://issues.apache.org/jira/browse/ARROW-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wes McKinney resolved ARROW-1960.
---------------------------------
Resolution: Won't Fix
Assignee: Wes McKinney
Since TensorFlow is a very large library to import unprompted, the best advice for this issue is "import tensorflow before pyarrow" until the compiler issues are resolved
> [Python] Pre-emptively import TensorFlow if it is available
> -----------------------------------------------------------
>
> Key: ARROW-1960
> URL: https://issues.apache.org/jira/browse/ARROW-1960
> Project: Apache Arrow
> Issue Type: Bug
> Components: Python
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Priority: Major
>
> To work around some ABI incompatibility issues with libstdc++ (TF is using a newer compiler), we should consider importing tensorflow first if it is available before loading Arrow's shared libraries built with the manylinux1 toolchain. See discussion in
> https://github.com/apache/arrow/issues/1450
> One question is whether TensorFlow's symbols will clash with Arrow's in some way that might impact its functioning.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)