issue_comments: 511126208

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/1603#issuecomment-511126208 https://api.github.com/repos/pydata/xarray/issues/1603 511126208 MDEyOklzc3VlQ29tbWVudDUxMTEyNjIwOA== 1197350 2019-07-13T14:27:32Z 2019-07-13T14:27:32Z MEMBER

After spending a few hours on the issue tracker yesterday, it became clear to me that the issue--more flexible indexes--is a major blocker on many high-priority features going forward.

In #2639, @shoyer started to address this. In that now merged-PR, he outlined the following steps, each of which needs its own PR:

  • [x] In #2639 Indexes are recreated from coordinates every time a new DataArray or Dataset is created.
  • [ ] Refactor indexes to be propagated explicitly in xarray operations. This will facilitate future API changes, when indexes will no longer only be associated with dimensions. I will probably add some testing decorator that can be used to mark part of a test as including no creation of default indexes.
  • [ ] Add explicit entries into indexes for MultiIndex levels that are checked instead of MultiIndex variables. Still no public API changes (aside from adding more entries to .indexes).
  • [ ] Support arbitrary coordinates in indexes.

So the best way to make progress on all manner of higher-level xarray feature requests is to start working through the next three items in this list.

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