issues: 1657396474
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1657396474 | PR_kwDOAMm_X85NxJ61 | 7731 | Continue to use nanosecond-precision Timestamps in precision-sensitive areas | 6628425 | closed | 0 | 9 | 2023-04-06T13:06:50Z | 2023-04-13T15:17:14Z | 2023-04-13T14:58:34Z | MEMBER | 0 | pydata/xarray/pulls/7731 | This addresses the remaining cftime-related test failures in #7707 by introducing a function that always returns a nanosecond-precision Timestamp object. Despite no corresponding test failures, for safety I grepped and went ahead and replaced the While in principle I think it would be fine if
|
{
"url": "https://api.github.com/repos/pydata/xarray/issues/7731/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | pull |