issue_comments: 576670981

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/3709#issuecomment-576670981 https://api.github.com/repos/pydata/xarray/issues/3709 576670981 MDEyOklzc3VlQ29tbWVudDU3NjY3MDk4MQ== 35968931 2020-01-21T13:02:34Z 2020-01-21T13:02:34Z MEMBER

IMHO, I would rather see this maintained in a separate project

Yeah that's a fair point. I think this is another case where the ecosystem of packages orbiting xarray could do with being more explicitly organised.

Reasons for direct integration in xarray: - Availability to all users: Functionality should be of general interest to anyone using xarray with jupyter, it's not domain-specific at all, - Makes writing robust code a bit easier because can then rely on private xarray methods for parsing indexers and so on

Reasons for a separate xarray-interactive repository: - Keeps developer maintenance / issue tracking separate - If plotting library-specific interfaces are desired they can be adding without cluttering main repo

I guess either way I could just write it in a separate repo and if in future we decided to include it in xarray master then move it.

@philippjfr @rabernat would be interested in your perspectives as developers/users of these downstream libraries? Would this be useful or not really?

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