[
https://issues.apache.org/jira/browse/ARROW-13806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422255#comment-17422255
]
Micah Kornfield commented on ARROW-13806:
-----------------------------------------
So I've started implementation. The approach I'm going to go with:
- Conversion to Pandas will use DateOffset (object dtype).
- Conversion to Python will used a named tuple
- Inference from python will detect DateOffset, relevativedelta or the named
tuple
- Conversion (once type is inferred or provided) from python will use duck
typing that should support timedelta (timedelta is inferred today to be
duration and that won't change), DateOffset, relativedelta and the named tuple
of export. It will ignore "absolute" fields in the latter two and also ignore
leapdays in relativedelta.
Please provide feedback if this is reasonable.
> [Python] Add conversion to/from Pandas/Python for Month, Day Nano Interval
> Type
> -------------------------------------------------------------------------------
>
> Key: ARROW-13806
> URL: https://issues.apache.org/jira/browse/ARROW-13806
> Project: Apache Arrow
> Issue Type: New Feature
> Components: Python
> Reporter: Micah Kornfield
> Assignee: Micah Kornfield
> Priority: Major
> Fix For: 6.0.0
>
>
> [https://github.com/apache/arrow/pull/10177] has been merged we should
> support conversion to and from this type for standard python surface areas.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
