issues: 103380276
This data as json
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
103380276 | MDU6SXNzdWUxMDMzODAyNzY= | 552 | Dataset.to_dataframe() loses datetime64 timezone localization | 2002703 | closed | 0 | 2 | 2015-08-26T22:34:11Z | 2015-08-29T14:11:46Z | 2015-08-29T14:11:46Z | CONTRIBUTOR | Not sure if feature or bug, but definitely made me look twice. ```
I'd expected to see the DataFrame index maintaining its local timezone info:
That said, the UTC that I actually get back is the same time so math should still work. I'm opening this issue mostly as a matter for discussion -- feel free to close if you think xray should be pushing users towards UTC. |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/552/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | 13221727 | issue |