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

Posted to jira@arrow.apache.org by "Rok Mihevc (Jira)" <ji...@apache.org> on 2023/01/11 07:12:04 UTC

[jira] [Commented] (ARROW-970) [Python] Accidentally calling pyarrow.Table() should not segfault process

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

Rok Mihevc commented on ARROW-970:
----------------------------------

This issue has been migrated to [issue #16569|https://github.com/apache/arrow/issues/16569] on GitHub. Please see the [migration documentation|https://github.com/apache/arrow/issues/14542] for further details.

> [Python] Accidentally calling pyarrow.Table() should not segfault process
> -------------------------------------------------------------------------
>
>                 Key: ARROW-970
>                 URL: https://issues.apache.org/jira/browse/ARROW-970
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Python
>    Affects Versions: 0.3.0
>            Reporter: Wes McKinney
>            Assignee: Wes McKinney
>            Priority: Major
>             Fix For: 0.4.0
>
>
> While we need not go crazy with null-pointer checks, the code that gets executed by {{repr(pyarrow.Table())}} should result in a more helpful error message



--
This message was sent by Atlassian Jira
(v8.20.10#820010)