issue_comments: 42981862
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/pull/125#issuecomment-42981862 | https://api.github.com/repos/pydata/xarray/issues/125 | 42981862 | MDEyOklzc3VlQ29tbWVudDQyOTgxODYy | 1217238 | 2014-05-13T16:56:33Z | 2014-05-13T16:56:33Z | MEMBER | Indeed, it would be nice to make that consistent! I was making some effort to not automatically convert python or netCDF4 datetime objects into numpy.datetime64, for the hypothetical situation where people care about dates before 1677 or aren't using standard calendars (but this will change with #126). But if that's too complicated, feel free to insist on the pandas approach of converting everything to nanosecond datetime64. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
33307883 |