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 2019/08/21 23:31:00 UTC

[jira] [Updated] (ARROW-4746) [C++/Python] PyDataTime_Date wrongly casted to PyDataTime_DateTime

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

Wes McKinney updated ARROW-4746:
--------------------------------
    Fix Version/s: 0.15.0

> [C++/Python] PyDataTime_Date wrongly casted to PyDataTime_DateTime
> ------------------------------------------------------------------
>
>                 Key: ARROW-4746
>                 URL: https://issues.apache.org/jira/browse/ARROW-4746
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++, Python
>            Reporter: Uwe L. Korn
>            Priority: Major
>              Labels: pypy
>             Fix For: 0.15.0
>
>
> As mentioned in https://bitbucket.org/pypy/pypy/issues/2842/running-pyarrow-on-pypy-segfaults#comment-50670536, we currently access a {{PyDataTime_Date}} object with a {{PyDataTime_DateTime}} cast in {{PyDateTime_DATE_GET_SECOND}} in our code in two instances. While CPython is able to deal with this wrong usage, PyPy is not able to do so. We should separate the path here into one that deals with dates and another that deals with datetimes.
> Reproducible code:
> {code:java}
> pa.array([datetime.date(2018, 5, 10)], type=pa.date64()){code}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)