jorisvandenbossche commented on issue #41162:
URL: https://github.com/apache/arrow/issues/41162#issuecomment-2100640468
I am not entirely sure if we should change this (apart from that it is a
breaking change, there is also the code complexity it would add and whether
that would be worth it).
It might be worth checking how involved it would be to change this, to be
able to better judge that complexity argument.
Note that you can preserve the timezone information for nested timestamps as
well with the `timestamp_as_object` keyword (which I didn't include in the
examples above), but of course then you have to live with object-dtype arrays:
```python
# using the last list array from above
>>> arr.to_pandas(timestamp_as_object=True).to_numpy()
array([array([datetime.datetime(2024, 1, 1, 13, 0, tzinfo=<DstTzInfo
'Europe/Paris' CET+1:00:00 STD>)],
dtype=object)
],
dtype=object)
```
--
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]
