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/2754#issuecomment-462098888,https://api.github.com/repos/pydata/xarray/issues/2754,462098888,MDEyOklzc3VlQ29tbWVudDQ2MjA5ODg4OA==,6628425,2019-02-10T02:53:23Z,2019-02-10T02:53:23Z,MEMBER,"> What is still missing once 0.12 is released (plotting and resampling)? I don't have the full overview there.

@mathause indeed we've made a lot of progress.  A few remaining missing things that come to mind (there could be others) are:
- Support for missing values in arrays of cftime objects (I should probably create an issue for this)
- Possible PeriodIndex-like functionality with cftime objects (#2481)
- [`coarsen`](https://github.com/pydata/xarray/blob/8a1a8a1f13462440543581cd12fb96f22f0748bc/xarray/core/common.py#L593-L647) (coming in the next version of xarray) still needs to be updated to work with cftime coordinates (waiting on #2668 before starting on that) 

Out of those three, `coarsen` is probably the highest priority on my list at the moment (the other two would require some more careful thought).  ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,407864596
https://github.com/pydata/xarray/issues/2754#issuecomment-462098476,https://api.github.com/repos/pydata/xarray/issues/2754,462098476,MDEyOklzc3VlQ29tbWVudDQ2MjA5ODQ3Ng==,6628425,2019-02-10T02:42:12Z,2019-02-10T02:42:12Z,MEMBER,Thanks for your thoughts @shoyer; I like your suggested approach.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,407864596
https://github.com/pydata/xarray/issues/2754#issuecomment-461983092,https://api.github.com/repos/pydata/xarray/issues/2754,461983092,MDEyOklzc3VlQ29tbWVudDQ2MTk4MzA5Mg==,1217238,2019-02-08T23:33:37Z,2019-02-08T23:33:37Z,MEMBER,"From a design perspective, I would consider adding an optional `use_cftime` argument:
- The default value `use_cftime=None` would match current behavior
` `use_cftime=True` would mean always use cftime (no warnings)
- `use_cftime=False` would mean never use cftime (error instead)","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,407864596
https://github.com/pydata/xarray/issues/2754#issuecomment-461982693,https://api.github.com/repos/pydata/xarray/issues/2754,461982693,MDEyOklzc3VlQ29tbWVudDQ2MTk4MjY5Mw==,1217238,2019-02-08T23:31:23Z,2019-02-08T23:31:23Z,MEMBER,+1 for adding an option to always use CF datetimes. I would probably start with putting it on `open_dataset()` rather than making it global -- local options make it much easier to follow control flow.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,407864596
https://github.com/pydata/xarray/issues/2754#issuecomment-461880601,https://api.github.com/repos/pydata/xarray/issues/2754,461880601,MDEyOklzc3VlQ29tbWVudDQ2MTg4MDYwMQ==,10194086,2019-02-08T17:27:20Z,2019-02-08T17:27:48Z,MEMBER,"I just ran into the problem trying to `xr.concat` two files - one that runs from 2000 to 2150, the second from 2151 to 2300. They have a mix of `Timestamp` and `cftime.DatetimeGregorian` in the time vector which, obviously can not be saved to disk. (I.e. concat worked but not to_netcdf).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,407864596
https://github.com/pydata/xarray/issues/2754#issuecomment-461830931,https://api.github.com/repos/pydata/xarray/issues/2754,461830931,MDEyOklzc3VlQ29tbWVudDQ2MTgzMDkzMQ==,10194086,2019-02-08T15:02:21Z,2019-02-08T15:02:21Z,MEMBER,"Yes, I meant this warning.

Thanks, I understand better now - it makes sense to throw a warning when you unexpectedly get a `cftime` instead of pandas dates. 

An `option` might be a good way to get consistent datetimes. Especially as the capabilities with `cftime` are progressing. What is still missing once 0.12 is released (plotting and resampling)? I don't have the full overview there.

Btw: I am really thrilled to be able to have datetime irrespective of the calendar.

","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,407864596
https://github.com/pydata/xarray/issues/2754#issuecomment-461814892,https://api.github.com/repos/pydata/xarray/issues/2754,461814892,MDEyOklzc3VlQ29tbWVudDQ2MTgxNDg5Mg==,6628425,2019-02-08T14:11:53Z,2019-02-08T14:11:53Z,MEMBER,"Thanks @mathause -- I'm assuming you are referring to this warning, rather than an error?
```
//anaconda/envs/xarray-dev-37/bin/ipython:2: SerializationWarning: Unable to decode time axis into full numpy.datetime64 objects, continuing using dummy cftime.datetime objects instead, reason: dates out of range
```
The rationale for keeping this warning is that for standard calendars (like `'proleptic_gregorian'`) we use pandas/NumPy dates by default; therefore falling back to using cftime in this circumstance is a deviation from the default behavior, which might come as a surprise to some users.  

I wonder if it might make sense to offer an [option](http://xarray.pydata.org/en/stable/generated/xarray.set_options.html) in xarray to always decode times to cftime dates, even for standard calendar dates between years 1678 and 2262 (which, if set, could also silence this warning); this would be another possible solution for #1263.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,407864596