You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "David Li (Jira)" <ji...@apache.org> on 2021/05/28 00:01:20 UTC

[jira] [Closed] (ARROW-12899) [Python] Cython fails builds on some machines with a CResult[shared_ptr[const Foo]]] declaration

     [ https://issues.apache.org/jira/browse/ARROW-12899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Li closed ARROW-12899.
----------------------------
    Resolution: Not A Problem

Upgrading Cython fixed it (it turns out 0.29.21 was being used, not 0.29.23)

> [Python] Cython fails builds on some machines with a CResult[shared_ptr[const Foo]]] declaration
> ------------------------------------------------------------------------------------------------
>
>                 Key: ARROW-12899
>                 URL: https://issues.apache.org/jira/browse/ARROW-12899
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Python
>            Reporter: David Li
>            Assignee: David Li
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> On the Conbench machines, the Cython code is failing to build:
> {noformat}
> Error compiling Cython file:
> ------------------------------------------------------------
> ...
>         @staticmethod
>         CStatus Open(const shared_ptr[CRandomAccessFile]& file,
>                      CMemoryPool* pool,
>                      unique_ptr[ORCFileReader]* reader)
>  
>         CResult[shared_ptr[const CKeyValueMetadata]] ReadMetadata()
>                                 ^
> ------------------------------------------------------------
>  
> pyarrow/_orc.pxd:42:33: Expected ']', found 'CKeyValueMetadata'{noformat}
> Cython appears not to like the {{CResult[shared_ptr[const CKeyValueMetadata]]]}}, though this seems to only happen on some machines, even if using the same Cython version. Declaring a Status-returning variant seems to work around it.



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