issues: 1419972576
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1419972576 | PR_kwDOAMm_X85BXqCR | 7201 | Emit a warning when converting datetime or timedelta values to nanosecond precision | 6628425 | closed | 0 | 3 | 2022-10-23T23:17:07Z | 2022-10-26T16:07:16Z | 2022-10-26T16:00:33Z | MEMBER | 0 | pydata/xarray/pulls/7201 | This PR addresses #7175 by converting datetime or timedelta values to nanosecond precision even if pandas does not. For the time being we emit a warning when pandas does not do the conversion, but we do (right now this is only in the development version of pandas). When things stabilize in pandas we can consider relaxing this constraint in xarray as well. This got a little bit more complicated due to the presence of timezone-aware datetimes in pandas, but hopefully the tests cover those cases now.
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/7201/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
13221727 | pull |