issue_comments: 445845065
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/pull/2553#issuecomment-445845065 | https://api.github.com/repos/pydata/xarray/issues/2553 | 445845065 | MDEyOklzc3VlQ29tbWVudDQ0NTg0NTA2NQ== | 35968931 | 2018-12-10T14:59:30Z | 2018-12-10T15:21:05Z | MEMBER |
I think that's probably the case, but I also think that those edge cases will be so specific that maybe we don't have to explicitly support them. We could just say that anyone who has a combination of datasets that is that funky can just concatenate them themselves?
I agree, two separate functions is a lot more intuitive than having The only problem with that idea is that both of these functions should be options for
That would be great. Then I could start using the master branch of xarray again in my code, while we redo the public API. If I set |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
379415229 |