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,"> This could probably either be done in a separate package

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
https://github.com/pydata/xarray/issues/2164#issuecomment-390518653,https://api.github.com/repos/pydata/xarray/issues/2164,390518653,MDEyOklzc3VlQ29tbWVudDM5MDUxODY1Mw==,1550771,2018-05-20T22:45:41Z,2018-05-21T03:14:33Z,NONE,"Thanks for the detailed example, I've been able to reproduce the issue. Part of it is that we need to add the new type(s) to ``holoviews.util.datetime_types``. Secondly it seems like bokeh's date conversion code will also have to be made aware of this new type somehow (I haven't investigated that yet).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,324740017