issue_comments: 404830736
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/2164#issuecomment-404830736 | https://api.github.com/repos/pydata/xarray/issues/2164 | 404830736 | MDEyOklzc3VlQ29tbWVudDQwNDgzMDczNg== | 810663 | 2018-07-13T13:17:44Z | 2018-07-13T13:17:44Z | NONE |
Why a separate package and not in nc-time-axis? (Or alternatively, just in cftime, as you say) FWIW https://github.com/SciTools/nc-time-axis/issues/16 tried to get the ball rolling on clarifications around the CalendarDateTime object. That was necessary in the days when there was a single PhoneyDateTime object, that didn't have calendar information associated with it. It seems that some refactoring is very plausible in nc-time-axis at this point. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
324740017 |