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

Posted to jira@arrow.apache.org by "Sanjiban Sengupta (Jira)" <ji...@apache.org> on 2022/01/10 15:03:00 UTC

[jira] [Assigned] (ARROW-14448) [Python] Update pyarrow.array() docstring note on timestamp (timezone) conversion

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

Sanjiban Sengupta reassigned ARROW-14448:
-----------------------------------------

    Assignee: Sanjiban Sengupta

> [Python] Update pyarrow.array() docstring note on timestamp (timezone) conversion
> ---------------------------------------------------------------------------------
>
>                 Key: ARROW-14448
>                 URL: https://issues.apache.org/jira/browse/ARROW-14448
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Python
>            Reporter: Joris Van den Bossche
>            Assignee: Sanjiban Sengupta
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 7.0.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The current {{pa.array(..)}} docstring has the following note:
> bq. Localized timestamps will currently be returned as UTC (pandas’s native representation). Timezone-naive data will be implicitly interpreted as UTC.
> This is IMO quite confusing. While _technically_ somewhat correct (we do store UTC values under the hood for timezone aware data, and values "as if" in UTC for timezone naive data), it's not what the user actually gets returned. The type of the returned array does preserve the timezone if possible, or will have no timezone (also no UTC) when converted from naive timestamps.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)