AlenkaF commented on issue #39539: URL: https://github.com/apache/arrow/issues/39539#issuecomment-2017668110
Thank you for contributing to the discussion @jonmmease. I see that libraries are working around this by defining date and time types as protocol DATETIME data type with Apache Arrow C Data Interface format string (example `tdD` for `date32`, `tdm` for `date64` etc, see [Polars code](https://github.com/pola-rs/polars/blob/53f55367d1428b6d4ab51a7b17a8dbf4c003ac43/py-polars/polars/interchange/utils.py#L48-L50) and [pandas code](https://github.com/pandas-dev/pandas/blob/4f145b3a04ac2e9167545a8a2a09d30856d9ce42/pandas/core/interchange/utils.py#L84-L92)). I do not mind going about it in similar way in PyArrow until date is added to the dataframe protocol spec. Also adding the option to consume this data type. It would be ideal, though, that this is clarified and set in the protocol first. @jorisvandenbossche, what do you think? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
