issue_comments: 660154476

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/4234#issuecomment-660154476 https://api.github.com/repos/pydata/xarray/issues/4234 660154476 MDEyOklzc3VlQ29tbWVudDY2MDE1NDQ3Ng== 1610850 2020-07-17T14:58:53Z 2020-07-17T14:58:53Z CONTRIBUTOR

The only things I can think of that would make sense initially in an accessor would be to_cupy/from_cupy to move back and forth from the GPU, plus maybe an alias for get to from_cupy to match the cupy API.

An accessor does seem like a reasonable place to put that logic, but it also seems like a tiny amount of code to make, ship and maintain a separate package for. Plus those methods will either need to be used or duplicated in the core codebase to support things like plotting.

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