You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Joris Van den Bossche (Jira)" <ji...@apache.org> on 2021/04/26 15:39:01 UTC

[jira] [Commented] (ARROW-12526) [Python] Pre-generate pyarrow.compute members

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

Joris Van den Bossche commented on ARROW-12526:
-----------------------------------------------

In general, we commit generated code, I think.

Wondering, would something like ARROW-10316 also already help? Although I suppose not for static tools, that probably only makes the interactive use nicer.

> [Python] Pre-generate  pyarrow.compute members
> ----------------------------------------------
>
>                 Key: ARROW-12526
>                 URL: https://issues.apache.org/jira/browse/ARROW-12526
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Python
>    Affects Versions: 4.0.0
>            Reporter: Adam Lippai
>            Priority: Minor
>             Fix For: 5.0.0
>
>
> Static analysis tools (e.g. pylint) don't recognize simple members like pyarrow.compute.equal, they report is as _missing_. Generating file (well a file imported by this file I assume) [https://github.com/apache/arrow/blob/master/python/pyarrow/compute.py] instead of runtime wrapping of the functions would improve the developer experience.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)