issue_comments: 461814892

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/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 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