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/789#issuecomment-219928912,https://api.github.com/repos/pydata/xarray/issues/789,219928912,MDEyOklzc3VlQ29tbWVudDIxOTkyODkxMg==,2443309,2016-05-18T05:29:20Z,2016-05-18T05:29:20Z,MEMBER,"@brews - I think this issue (https://github.com/pydata/pandas/issues/7307) covers the main gist of what we're talking about here.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,139956689
https://github.com/pydata/xarray/issues/789#issuecomment-195031692,https://api.github.com/repos/pydata/xarray/issues/789,195031692,MDEyOklzc3VlQ29tbWVudDE5NTAzMTY5Mg==,2443309,2016-03-10T20:23:26Z,2016-03-10T20:23:26Z,MEMBER,"> This might make slightly more sense in a related but distinct project to xarray.

@shoyer - are you thinking `xarray` would fall back to a `CustomDatetimeIndex` for non-standard calendars?

I actually don't think it would be all that hard to do this.  @jswhit's [`netcdftime`](https://github.com/Unidata/netcdf4-python/blob/master/netcdftime/netcdftime.py) module is at least a good starting point. There's a lot to build on in `netcdftime` and `pandas.tseries.index`. I'd actually say this should be targeted at Pandas (probably as a side project) rather than `xarray`.  Ultimately, it would be nice to be able to move timeseries back and forth without any hassle. 

I'd be happy to help pull this together, although, I won't be able to make significant contributions until the summer. Is anyone chomping at the bit to work on something like this?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,139956689