home / github / issues

Menu
  • Search all tables
  • GraphQL API

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., x[index] could result in an object that could not be indexed properly. This resulted in broken behavior with dask's new _meta attribute.

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 blockwise_meta helper function: ```

  return meta.astype(dtype)

E AttributeError: 'ImplicitToExplicitIndexingAdapter' object has no attribute 'astype' ```

cc @mrocklin @pentschev

  • [x] Tests added
{
    "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

Links from other tables

  • 0 rows from issues_id in issues_labels
  • 3 rows from issue in issue_comments
Powered by Datasette · Queries took 74.856ms · About: xarray-datasette