issues: 456963929
This data as json
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
456963929 | MDExOlB1bGxSZXF1ZXN0Mjg4ODcwMDQ0 | 3027 | Ensure explicitly indexed arrays are preserved | 1217238 | closed | 0 | 3 | 2019-06-17T14:21:18Z | 2019-06-23T16:53:11Z | 2019-06-23T16:49:23Z | MEMBER | 0 | pydata/xarray/pulls/3027 | Fixes https://github.com/pydata/xarray/issues/3009 Previously, indexing an ImplicitToExplicitIndexingAdapter object could directly return an ExplicitlyIndexed object, which could not be indexed normally, e.g., I'm pretty sure this fix is appropriate, but it does introduce two failing tests with xarray on dask master. In particular, there are now errors raised inside two tests from dask's
cc @mrocklin @pentschev
|
{ "url": "https://api.github.com/repos/pydata/xarray/issues/3027/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
13221727 | pull |