issue_comments: 256541189

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/1062#issuecomment-256541189 https://api.github.com/repos/pydata/xarray/issues/1062 256541189 MDEyOklzc3VlQ29tbWVudDI1NjU0MTE4OQ== 12307589 2016-10-27T04:01:55Z 2016-10-27T04:01:55Z CONTRIBUTOR

I think using a more informative error when particularly year and month are used would be the right way to go. It would also probably be fine to require integer months/years, but Pandas also has weird behavior:

In[6]: pd.to_timedelta(1, 'M') Out[6]: Timedelta('30 days 10:29:06') In[7]: pd.to_timedelta(1.5, 'M') Out[7]: Timedelta('30 days 10:29:06')

Because of this it would take a significant rework of decode_cf_datetime in conventions.py to actually implement integer months working properly.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   185441216