issue_comments: 129102650
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/issues/521#issuecomment-129102650 | https://api.github.com/repos/pydata/xarray/issues/521 | 129102650 | MDEyOklzc3VlQ29tbWVudDEyOTEwMjY1MA== | 2443309 | 2015-08-09T04:03:34Z | 2015-08-09T04:03:34Z | MEMBER | We try to cast all the time variables to a pandas time index. This gives xray the ability to use many of the fast and fancy timeseries tools that pandas has. One consequence of that is that non-standard calendars, such as the "noleap" calendar must have dates inside the valid range of the standard calendars (1678 and 2226). Does that make since? Ideally, numpy and pandas would support custom calendars but they don't so, at this point, we're bound to there limits. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
99836561 |