issue_comments: 672812271

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/4336#issuecomment-672812271 https://api.github.com/repos/pydata/xarray/issues/4336 672812271 MDEyOklzc3VlQ29tbWVudDY3MjgxMjI3MQ== 6628425 2020-08-12T11:20:32Z 2020-08-12T11:20:32Z MEMBER

Indeed calendar-agnostic cftime.datetime objects are not supported. I agree error messages and documentation could be improved regarding this. We often use cftime.datetime as a shorthand to indicate that any one of cftime.DatetimeNoLeap, cftime.DatetimeGregorian, cftime.DatetimeProlepticGregorian, cftime.DatetimeJulian, cftime.Datetime360Day, cftime.DatetimeAllLeap (all subclasses of cftime.datetime) could be passed as inputs, even though cftime.datetime itself is not supported.

The primary cftime_range tests can be found here, where we do test calendar-aware datetime inputs of all calendar types.

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