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/1062#issuecomment-256539119,https://api.github.com/repos/pydata/xarray/issues/1062,256539119,MDEyOklzc3VlQ29tbWVudDI1NjUzOTExOQ==,2443309,2016-10-27T03:42:14Z,2016-10-27T03:42:14Z,MEMBER,"@mcgibbon - I'm not sure what to do here then. There is a related discussion [here](https://github.com/Unidata/netcdf4-python/issues/434) that I think we should follow.

So I think we need a more informative error or to better use whatever error `netcdf4` throws.

For the record, I never want a month to equal 30.42 days. I understand why UDUNITS did that (because units should vary with time) -- but they should have taken it up with those who decided on our calendar systems 😉.  
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,185441216
https://github.com/pydata/xarray/issues/1062#issuecomment-256417556,https://api.github.com/repos/pydata/xarray/issues/1062,256417556,MDEyOklzc3VlQ29tbWVudDI1NjQxNzU1Ng==,2443309,2016-10-26T17:19:44Z,2016-10-26T17:19:44Z,MEMBER,"@mcgibbon - I actually just ran into this today as well.  I'd be happy to see something sensible added to our decoding. To start, why don't we only allow decoding of these units when the values are (like) integers. `16 years since 2000-01-01` is easy enough to decode but partial months/years can get tricky and error-prone since `10.84 months since 2016-01-01` requires us to make some decisions about the length of the month/year.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,185441216