issue_comments: 404541298

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/2164#issuecomment-404541298 https://api.github.com/repos/pydata/xarray/issues/2164 404541298 MDEyOklzc3VlQ29tbWVudDQwNDU0MTI5OA== 6628425 2018-07-12T14:55:59Z 2018-07-12T14:55:59Z MEMBER

I think a quick and dirty fix could be to add nc-time-axis as an optional dependency, and convert any cftime.datetime objects encountered in plotting routines to nc_time_axis.CalendarDateTime objects before passing them to matplotlib.

But I wonder if there is potentially room for improvement upstream in cftime? Should we need to convert to these proxy objects before plotting or might there be a way to make cftime objects themselves more friendly to use with matplotlib? That could have benefits for multiple libraries (not just xarray).

@pelson @lbdreyer @ocefpaf (developers of nc-time-axis and Iris) -- it seems you have grappled with this problem a fair bit already. Have you thought about those questions before?

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